1 | environment: |
---|
2 | |
---|
3 | # SDK v7.0 MSVC Express 2008's SetEnv.cmd script will fail if the |
---|
4 | # /E:ON and /V:ON options are not enabled in the batch script interpreter |
---|
5 | # See: http://stackoverflow.com/a/13751649/163740 |
---|
6 | # 2018-01-19 PAK: probably irrelevant now that we are using tinycc rather than msvc |
---|
7 | CMD_IN_ENV: "cmd /E:ON /V:ON /C obvci_appveyor_python_build_env.cmd" |
---|
8 | |
---|
9 | # Workaround for https://github.com/conda/conda-build/issues/636 |
---|
10 | PYTHONIOENCODING: "UTF-8" |
---|
11 | |
---|
12 | matrix: |
---|
13 | # Note: Because we have to separate the py2 and py3 components due to compiler version, we have a race condition for non-python packages. |
---|
14 | # Not sure how to resolve this, but maybe we should be tracking the VS version in the build string anyway? |
---|
15 | - TARGET_ARCH: "x86" |
---|
16 | CONDA_PY: "27" |
---|
17 | PY_CONDITION: "python >=2.7,<3" |
---|
18 | CONDA_INSTALL_LOCN: "C:\\Miniconda" |
---|
19 | # - TARGET_ARCH: "x86" |
---|
20 | # CONDA_PY: "34" |
---|
21 | # PY_CONDITION: "python >=3.4,<3.5" |
---|
22 | # CONDA_INSTALL_LOCN: "C:\\Miniconda3" |
---|
23 | - TARGET_ARCH: "x86" |
---|
24 | CONDA_PY: "35" |
---|
25 | PY_CONDITION: "python >=3.5" |
---|
26 | CONDA_INSTALL_LOCN: "C:\\Miniconda35" |
---|
27 | - TARGET_ARCH: "x64" |
---|
28 | CONDA_PY: "27" |
---|
29 | PY_CONDITION: "python >=2.7,<3" |
---|
30 | CONDA_INSTALL_LOCN: "C:\\Miniconda-x64" |
---|
31 | # - TARGET_ARCH: "x64" |
---|
32 | # CONDA_PY: "34" |
---|
33 | # PY_CONDITION: "python >=3.4,<3.5" |
---|
34 | # CONDA_INSTALL_LOCN: "C:\\Miniconda3-x64" |
---|
35 | - TARGET_ARCH: "x64" |
---|
36 | CONDA_PY: "35" |
---|
37 | PY_CONDITION: "python >=3.5" |
---|
38 | CONDA_INSTALL_LOCN: "C:\\Miniconda35-x64" |
---|
39 | |
---|
40 | # We always use a 64-bit machine, but can build x86 distributions |
---|
41 | # with the TARGET_ARCH variable (which is used by CMD_IN_ENV). |
---|
42 | platform: |
---|
43 | - x64 |
---|
44 | |
---|
45 | install: |
---|
46 | # Set the CONDA_NPY, although it has no impact on the actual build. |
---|
47 | # We need this because of a test within conda-build. |
---|
48 | - cmd: set CONDA_NPY=19 |
---|
49 | |
---|
50 | # Remove cygwin (and therefore the git that comes with it). |
---|
51 | # 2018-01-19 PAK: probably irrelevant since we already pulled the repo |
---|
52 | #- cmd: rmdir C:\cygwin /s /q |
---|
53 | |
---|
54 | # Set the conda path; would be nice to do this |
---|
55 | - cmd: path %CONDA_INSTALL_LOCN%\\Scripts;%PATH% |
---|
56 | |
---|
57 | # Use the pre-installed Miniconda for the desired arch |
---|
58 | # |
---|
59 | # However, it is really old. So, we need to update some |
---|
60 | # things before we proceed. That seems to require it being |
---|
61 | # on the path. So, we temporarily put conda on the path |
---|
62 | # so that we can update it. Then we remove it so that |
---|
63 | # we can do a proper activation. |
---|
64 | - cmd: conda update --yes --quiet conda python |
---|
65 | - cmd: call "%CONDA_INSTALL_LOCN%\Scripts\activate.bat" |
---|
66 | - cmd: conda config --add channels conda-forge |
---|
67 | - cmd: conda config --set show_channel_urls true |
---|
68 | - cmd: conda install --yes --quiet obvious-ci |
---|
69 | - cmd: conda install --yes --quiet numpy toolchain scipy cython cffi |
---|
70 | - cmd: conda install --yes --channel conda-forge pyopencl |
---|
71 | # 2018-01-19 PAK: 3rd party packages might need msvc, so %CMD_IN_ENV% may be needed for pip |
---|
72 | - cmd: pip install bumps unittest-xml-reporting tinycc |
---|
73 | |
---|
74 | build_script: |
---|
75 | # Build the project |
---|
76 | - "%CMD_IN_ENV% python setup.py build" |
---|
77 | |
---|
78 | test_script: |
---|
79 | # Run the project tests |
---|
80 | - "%CMD_IN_ENV% python -m sasmodels.model_test dll all" |
---|