Cygwin support broken in VS2015 and VS2017 images
Cygwin is not fully functional in older images.
Examples:
VS2019 is working: https://ci.appveyor.com/project/rleigh-codelibre/libtiff-didfs/builds/35409332/job/ohooewb03btl5f4r
VS2017 is broken: https://ci.appveyor.com/project/rleigh-codelibre/libtiff-didfs/builds/35402106/job/udf8xh5jqqea03ay
VS2015 is broken: https://ci.appveyor.com/project/rleigh-codelibre/libtiff-didfs/builds/35149670
VS2015 was working a few months back: https://ci.appveyor.com/project/rleigh-codelibre/libtiff-didfs/builds/33361475
I dropped the cache, but it looks like the problem is a DLL incompatibility since the program is on the path but can't be loaded. The fix might be to update the Cygwin version in the older VS2017, VS2015 images so that new package installations will work and be functional.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by rleigh on 25 Sep, 2020 04:35 PM
To add a bit more detail, the program in question is "cmake", which I install using the Cygwin setup64 executable. It is installed and present under C:\Cygwin64\bin\cmake.exe but the executable won't run. In the first two builds linked to above, I added extra logging of the environment, directories and the executable itself before trying to run it in various ways.
Locally, I have the same binary installed from the same package with the same file size and it works perfectly. So I think there's some mismatch in the older images which prevents it from running.