Am 04.08.2025 um 15:03 schrieb Old, Oliver via Cygwin:
BTW, what exactly is the "Windows-native tool"?A tool built to run on Microsoft's CRT, so not a Cygwin program.So, shouldn't you be complaining abount PowerShell as well?I'm only using CMD as a launcher here (and made sure it does not modify the input in unexpected ways). This is not about how a shell treats commands, it's just about how a command line is interpreted by the launched process. I validated this with Sysinternals Process Monitor.Isn't that the responsibility of the "Windows-native tool"? If it invokes cygwin build tool, it should pass the arguments in a way that conforms to cygwin's conventions.CMake is not aware that it needs to generate Ninjafiles/Makefiles for Cygwin programs and currently can't be made aware AFAIK. I had to resort to a hack involving using undocumented CMAKE_<LANG>_COMPILER_ARG1 variables and a custom launcher tool that rewrites the command line. I wish I did not have to venture into unsupported/undocumented territory here.
Why don't you use the cygwin cmake?
OpenPGP_0x917D882CE22A6AD2_and_old_rev.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
