Michael Kutschke

I understand the question to be: 1. generate NMake Makefile with the wrapper script 2. build using nmake, not by calling cmake --build with the script 3. check that 2....

OK that is simpler, I will try that.

No it does not work. I tested this by explicitly setting an environment variable in the wrapper script and reading it in the CMakeLists.txt. The first run picks up the...

Next test, I did: 1. build with wrapper script in place 2. change CMakeLists.txt to trigger cmake to run 3. build again - works as expected 4. change cmake executable...

By the way, when I change the cmake command, it does not force a cmake rerun, I think that is probably a bug.

I think I fixed my problem, but it is debatable how nice it is. I call the script and read out the environment variables it sets. For INCLUDE: ``` execute_process(COMMAND...

It does not work, and I think it is because of the command line you generate: `cmd.exe /c "C:\\LegacyApp\\VisualStudio2015\\Common7\\Tools\\VsDevCmd.bat" && cmake -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_RULE_MESSAGES:BOOL=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=ON -G "\"NMake Makefiles\"" "\"-DCMAKE_MODULE_PATH:PATH=C:\\Program Files\\eCAL\\cmake\"" -DCMAKE_BUILD_TYPE:STRING=Release...

``` cmd.exe /c "C:\\LegacyApp\\VisualStudio2015\\Common7\\Tools\\VsDevCmd.bat && cmake -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_RULE_MESSAGES:BOOL=OFF -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=ON -G \"NMake Makefiles\" \"-DCMAKE_MODULE_PATH:PATH=C:\\Program Files\\eCAL\\cmake\" -DCMAKE_BUILD_TYPE:STRING=Release -DOFFLINE:STRING=ON -DCMAKE_C_COMPILER_FORCED:STRING=1 -DCMAKE_CXX_COMPILER_FORCED:STRING=1 C:\\Users\\uidj1662\\runtime-xcit-rcp.product\\test_yaaf\\projects\\build\\autogen && exit %%ERRORLEVEL%%" CMake Error: Could not create named generator "NMake...

OK, I'll test and if it doesn't work I can see if I can make time to work on it. Which branch is it in?

OK will do. I assume I can somehow trick it with single quotes.