[CMake] cmake generators on windows: nmake versus jom

[Verweij, Arjen]

Brad,

I found another repository with jom binaries. It works fine with 0.9.4.

Apparently the original link I used to download JOM was ancient.

Thanks,
Arjen

>-----Original Message-----
>From: cmake-bounces at cmake.org [mailto:cmake-bounces at cmake.org] On Behalf
>Of Verweij, Arjen
>Sent: woensdag 21 juli 2010 23:07
>To: cmake at cmake.org
>Subject: Re: [CMake] cmake generators on windows: nmake versus jom
>
>Hi,
>
>>The generators are testing and inspecting the toolchain.
>>Something is not building as expected so it reports the problem up
>>front rather than waiting for some subtle error when building the main
>>project.
>
>OK.
>
>>> "NMake Makefiles JOM"
>>[snip]
>>> -- FIXME: altered Windows.cmake for debugging purposes.
>>
>>What is this?  What was altered?
>
># uncomment these out to debug nmake and borland makefiles # uncommented
>by AVE message (STATUS "FIXME: altered Windows.cmake for debugging
>purposes.") SET(CMAKE_START_TEMP_FILE "") SET(CMAKE_END_TEMP_FILE "")
>SET(CMAKE_VERBOSE_MAKEFILE 1)
>
>I want to see all the compile flags. It turns out that for reasons
>unknown the default setting for CMAKE_BUILD_TYPE is Debug for MSVC7.1,
>causing all kinds of trouble like mixing debug and non-debug libraries
>when linking the executable.
>
>>> -- Check for working Fortran compiler: E:/Program
>>Files/Intel/Fortran/compiler80/IA32/BIN/ifort.exe
>>> -- Check for working Fortran compiler: E:/Program
>>Files/Intel/Fortran/compiler80/IA32/BIN/ifort.exe  -- works
>>
>>This means the basic capability to compile an executable seems to work,
>>at least the build tool does not return failure.
>>
>>Do you actually have JOM installed in the environment?
>
>It is in the path.
>
>>Please post CMakeError.log and CMakeOutput.log from the CMakeFiles
>>directory in the build tree.
>
>Enclosed.
>
>Thanks,
>Arjen