[cmake-developers] Peculiar issue for "NMake Makefiles JOM"

[Bill Hoffman]

>
> The CMakeError.log you requested was not too informative:
>
> bash.exe-3.1$ cat CMakeFiles/CMakeError.log
> Determining if the C compiler works failed with the following output:
>

Next step is to try it by hand.

Start with a clean build tree and your simple project.  Then run
cmake with --debug-trycompile option.

This will leave all the temp files in CMakeFiles.  You can then run it 
by hand and see what the error is.   There should be a makefile in 
CMakeTmp, that you can run jom or nmake in and see what the error 
actually is.

>
> bash.exe-3.1$
>
> i.e., two blank lines.
>
> I just checked download statistics from the mingw SourceForge site for
> the gcc-4.7.2 core package alone (not the sum of all gcc-4.7.2-related
> packages which, of course, has much larger download statistics) and it
> has averaged 20000 downloads (!) a month for the 7 months since its
> release.  That's a lot of developers and potential users of CMake on
> Windows.  Therefore, it would likely be a good idea to make most
> Windows-based generators (such as "NMake Makefiles" and "NMake
> Makefiles JOM") work correctly with the MinGW suite of compilers. I am
> assuming here this would be a fairly trivial task for a developer who
> was familiar with the CMake language-support infrastructure.

This type of stuff does no good in figuring out what is wrong.  I really 
don't care how popular it is.  However, now that you bring it up...  It 
also comes with its own make program which for the most part is far 
superior to nmake or jom.  gmake is able to do parallel builds much 
better, and they finally added the jobserver stuff to the mingw gmake, 
so I would say that is the build tool to use for that environment. 
ninja might be more interesting to look at as it is better than gmake in 
many ways.  However, I am thinking not many of those 20000 downloads 
would be interested in nmake or jom.

>