Before you start you need a Mingw-w64 toolchain for Linux, try installing the mingw-w64 package (Ubuntu, Suse, Fedora?) or get it from the Mingw-w64 website.
$ mkdir deps-mingw
$ cd deps-mingw
$ cmake -DCMAKE_TOOLCHAIN_FILE=../cmake/mingw32-w64-cross-travis.toolchain.cmake ../third-party/
$ make
$ cd ..
Check the pull request for the changes and the main issue for discussion. If you run into trouble check the Known Errors section at the end, or drop me a comment.
| #!/usr/bin/python3 | |
| # | |
| # Little script to check if Appveyor is stuck | |
| # | |
| # The return code is (2) if the build is considered stuck, (0) if not | |
| # stuck, and (1) for other errors | |
| import json | |
| import sys | |
| import requests |
os_can_exe() used by executable() actually checks PATHEXT. Behaviour in Vim is:
executable('no_such_file') returns 0
executable('file') returns 1 if file.bat,file.exe,etc exist ($PATHEXT)
executable('file.bat')returns 1
executable('file.exe')returns 1
This could lead to the misconception that, for example, executable("file.bat") being 1 implies that system(["file.bat"]) is expected to succeed, which is not true. But this is an issue with system([]) in windows and not with executable(). The notion of executable in Windows is fundamentaly a shell concept, because unlike UNIX there no notion of shebang and permission bits, that allows execution of non binary files.
Vim's system('string') interface is not always straightforward in Windows,
its behaviour can be downright unexpected involves an intricate set of options. Its primary purpose its to execute
a command in the shell (see &shell) in simple terms we can think that calling system('some command') is equivalent
to spawning a process with the following arguments
[&shell, &shellcmdflag, 'some command']
and sometimes this might be true but it also might not. Consider the following examples (I'm running in gVim 7.4/Windows 8)
CMake has two generatores using Make for windows.
MinGW Makefiles expects to run from the cmd shell (uses mingw32-make)