cryptoauthlib-sys 0.2.2

Automatically generated Rust bindings for CryptoAuthentication Library calls.
Documentation
environment:
  TWINE_USERNAME:
    secure: TEiy+eHGeQQIy9jUEpUNMA==
  TWINE_PASSWORD:
    secure: nGYP/oqo/DSfCQduEhhKGg==

  matrix:
    - PYTHON: "C:\\Python27"
      TAG_SCENARIO: true
    - PYTHON: "C:\\Python27-x64"
      TAG_SCENARIO: true
    - PYTHON: "C:\\Python35"
      TAG_SCENARIO: true
    - PYTHON: "C:\\Python35-x64"
      TAG_SCENARIO: true
    - PYTHON: "C:\\Python36"
      TAG_SCENARIO: true
    - PYTHON: "C:\\Python36-x64"
      TAG_SCENARIO: true
    - PYTHON: "C:\\Python37"
      TAG_SCENARIO: true
    - PYTHON: "C:\\Python37-x64"
      TAG_SCENARIO: true

install:
    - cmd: "%PYTHON%\\python.exe -m pip install --upgrade pip"
    - cmd: "%PYTHON%\\python.exe -m pip install --upgrade setuptools"
    - cmd: "%PYTHON%\\python.exe -m pip install --upgrade wheel"
    - cmd: "%PYTHON%\\python.exe -m pip install --upgrade pytest"
    - cmd: "%PYTHON%\\python.exe -m pip install --upgrade enum34"
    - cmd: "%PYTHON%\\python.exe -m pip install --upgrade twine"

before_build:
    - cd python
    - cmd: "git describe --exclude v* --tags --abbrev=0 >VERSION"

build_script:
    - cmd: "%PYTHON%\\python.exe setup.py bdist_wheel"

artifacts:
    - path: python\dist\*.whl

#on_success:
#  You can use this step to upload your artifacts to a public website.
#  See Appveyor's documentation for more details. Or you can simply
#  access your wheels from the Appveyor "artifacts" tab for your build.
deploy_script:
    - ps: if ($env:APPVEYOR_REPO_TAG -eq $TRUE -and $env:APPVEYOR_REPO_TAG_NAME -notlike "v*") { & ${env:PYTHON}\python.exe -m twine upload "dist\*.whl" --skip-existing }

for:
-
  matrix:
    only:
      - TAG_SCENARIO: true

  skip_non_tags: true