I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I had serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.