search

dev-cafe / autocmake

CMake plugin composer.
http://autocmake.org
BSD 3-Clause "New" or "Revised" License
42 stars 18 forks source link

ihrasko: improved test script for appveyor #24

Closed ghost closed 9 years ago

ghost commented 9 years ago

using shorter path testing both 32-bit and 64-bit Python versions downloading and using the latest 5.1.0 version of mingw-w64 compilers added comments

Script is run on 64-bit Windows OS. In that case it is good to use 64-bit compilers. Then it is possible to compile Dirac with and also without 64-bit integers on without problems. During execution 64-bit Mingw-w64 compilers are downloaded.

In script both 32 and 64-bit versions of Python are used (every commit runs two tests, see picture). But still it is "better" to use 64-bit Python. Reasons:

  1. I have not tested 32-bit Python with Dirac on 64-bit Windows for long time (but it should work, 32-bit Python on 32-bit Windows works good)
  2. It is possible to follow instructions from Dirac documentation to install packages needed to generate documentation - mingw32-make html ...

It is possible to use also Python 3, because it is already preinstalled at AppVeyor. But it looks autocmake is not adapted for Python 3.

test

bast commented 9 years ago

Thank you!

bast commented 9 years ago

Just a comment: Autocmake is in principle adapted to Python 3 (I use it almost exclusively on Python 3) but there may be some breakage when on Windows which we need to fix. I will soon merge this to master and test Appveyor by default.

ghost commented 9 years ago

It is not "Windows breakage". It appears also on Linux with Python 3, see picture. Reason is that Python 3 complains when string operations are used on types which are not strings. Stdout and stderr captured in exe function were in binary format and compared in tests against strings. In next Pull Request I changed this - stdout, stderr are strings. linux