With a new-style ctest script like this, you should set CTEST_BUILD_COMMAND
and CTEST_BUILD_FLAGS to specify the make executable and arguments to it if
you need values different than those ctest uses by default. If you set
those, there is no need to set the MAKECOMMAND in the cache.
HTH,
David
On Wed, Sep 24, 2008 at 8:12 PM, Wheeler, Frederick W (GE, Research) <
[EMAIL PROTECTED]> wrote:
> CMake List:
>
> Here is a snippet of a ctest script I'm using.
>
> ...
> CTEST_EMPTY_BINARY_DIRECTORY( "${CTEST_BINARY_DIRECTORY}" )
> FILE( WRITE "${CTEST_BINARY_DIRECTORY}/CMakeCache.txt"
> "${CTEST_INITIAL_CACHE}" )
> CTEST_CONFIGURE( BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res )
> CTEST_READ_CUSTOM_FILES( "${CTEST_SOURCE_DIRECTORY}" )
> CTEST_BUILD( BUILD "${CTEST_BINARY_DIRECTORY}" RETURN_VALUE res )
> CTEST_TEST( RETURN_VALUE res )
> ...
>
> The problem I'm having is that during the CTEST_BUILD command, 'make'
> (the default?) seems to be used, instead of the
> MAKECOMMAND:STRING=C:/cygwin/home/200006507/make -k that I put into
> the initial CMakeCache.txt with the FILE( WRITE ... command. Setting
> MAKECOMMAND in the initial cache used to work for me with earlier
> versions of ctest and the earlier style of ctest script.
>
> My question: Is there some special CTEST_ variable that needs to be
> set to the make I want to use?
>
> Another option I guess I have is to wait for cygwin to upgrade make to
> the newer version that works with the Makefiles produced by CMake.
> I'm sure that will happen any day now.
>
> Thanks,
> Fred Wheeler
> _______________________________________________
> CMake mailing list
> CMake@cmake.org
> http://www.cmake.org/mailman/listinfo/cmake
>
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
