From: Bruno H. <br...@cl...> - 2017-03-19 10:43:48
|
Hi Reini, > 3. I’m in the progress to add continuous integration via travis (linux, OS X) and appveyor (Windows). > ... > https://github.com/rurban/clisp/commit/7b64a9b41d74460dc361e117700eee9713601ea0 Can you make the builds work on a machine that has not only MSVC but also Cygwin installed? I'm asking because nowadays my preferred way to produce native Windows binaries is by using Cygwin as a development environment, see [1], as it - does not require to manually maintain a config.h (since it's fully autoconfiguring), - does not require the complexity in makemake.in regarding backslashes vs. slashes (since the build relies on GNU make, not nmake), - does not require to regularly update win32msvc/makefile.msvc* (the last update was in 2010!) In other words, is much much simpler. But it requires Cygwin tools. Or in the future, the Microsoft WSL [2] may be reliable enough for this task as well. Bruno [1] http://git.savannah.gnu.org/gitweb/?p=libsigsegv.git;a=blob;f=README.windows [2] https://msdn.microsoft.com/en-us/commandline/wsl/about |