Hi Jannick, > Le 13 janv. 2020 à 08:18, Jannick <[email protected]> a écrit : > > Hi Akim, > > looking into travis a bit, here something which might be easier (locally I > am working along the following lines as well): > - use the MSYS2 shell > (https://docs.travis-ci.com/user/reference/windows/#how-do-i-use-msys2), my > favorite unix-like shell on windows. bison, flex, m4, perl etc. are shipped > in its base package. Applying the script in the aforementioned link makes > sure that they are all found on PATH of each of the shells MSYS2, MINGW32 > and MINGW64. The following assumes using the MING64 shell. > - For doxygen say 'pacman -S doxygen'. > - For msvc compilation I usually use clang64 (install with, e.g., 'pacboy > clang:x') which usually looks for the installed MSVC compiler on the system. > - Using clang and ./configure in the MINGW64 shell: clang's triplet is not > well understood by config.sub, so some tweaks are needed to charm > ./configure and its friends. ;) Note that a shell-specific config.site > setting defaults is called by ./configure for each of the shells MSYS2, > MINGW32 and MINGW64. > > HTH.
It does! Thanks a lot for your input! Currently I'm fighting with another branch, and when I'm done with it, I'm start again on the CI for Windows. For some reason (i.e., being stupid), I had indeed not realized that the winflexbison port of course must include m4 in some way. So maybe I can use it. Again, thanks a lot! > Appveyor (https://www.appveyor.com/docs/build-environment) might be an > alternative to consider which apparently is widely used. I don't want to spend too much time learning many CI tools. Travis is already consuming quite some time of mine. Cheers!
