<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>RE: [CMake] Native build system invocation</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>>> ... you might be interested in using<BR>
>> the value of CMAKE_GENERATOR. There's a list of the values<BR>
>> it takes on, as well as some information about scripts that<BR>
>> Kitware uses to automate builds on the CMake Wiki:<BR>
>> <A HREF="http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest">http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest</A><BR>
>> You could have CMake write the value of CMAKE_GENERATOR to<BR>
>> a file that your python script reads after invoking CMake<BR>
>> and uses to run the native build system.<BR>
><BR>
> I think I have better idea: is it possible to create<BR>
> "compile" test with CTest? This test does nothing, just<BR>
> compiles all projects in debug\release mode.<BR>
The problem is that compile tests are run before<BR>
CMake has generated configuration files, etc. So you<BR>
would not be able to take advantage of<BR>
- your build settings unless you use CONFIGURE_FILE<BR>
with the IMMEDIATE keyword to guarantee the files<BR>
are created as CMake parses the CONFIGURE_FILE command;<BR>
- CMake's ability to compute dependencies, since<BR>
TRY_COMPILE is run during CMake's configuration phase.<BR>
<BR>
> CTest also aware of native build system so it seems like<BR>
> a perfect solution to me.<BR>
This is much more feasible. In fact, Kitware has a CMake test:<BR>
<A HREF="http://public.kitware.com/cgi-bin/viewcvs.cgi/Tests/SimpleInstall/?root=CMake">http://public.kitware.com/cgi-bin/viewcvs.cgi/Tests/SimpleInstall/?root=CMake</A><BR>
that runs nightly and appears to install itself as well.<BR>
<BR>
David</FONT>
</P>
</BODY>
</HTML>