<div>Then I cannot use the subproject separation, right?</div><div>It seems this is "feature" that got lost with the new style: <a href="http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest#Continuous_Builds_.28old_Style.29">http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest#Continuous_Builds_.28old_Style.29</a></div>
<div><br></div><div><br></div>Michele<br><br><div class="gmail_quote">On Fri, Aug 24, 2012 at 3:51 PM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><div class="gmail_quote">On Fri, Aug 24, 2012 at 9:45 AM, Michele Dolfi <span dir="ltr"><<a href="mailto:dolfimeth@gmail.com" target="_blank">dolfimeth@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote"><div>On Fri, Aug 24, 2012 at 3:24 PM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><br>
On Aug 24, 2012, at 9:01, Michele Dolfi <<a href="mailto:dolfimeth@gmail.com" target="_blank">dolfimeth@gmail.com</a>> wrote:<br>
<br>
> Hi all,<br>
><br>
> I started using CMake, CTest and CDash, with the simple targets Nightly, Continuous and Experimental: it works very well.<br>
> Now I would like to divide my project in subproject, so that a failure in compiling one small test is not affecting the full dashboard report. I read that ctest driver files are the way to go.<br>
><br>
> I quickly realized that include(CTest) was automatically setting many variables that are not there in a ctest driver script, i.e. CTEST_SITE, CTEST_BUILD_NAME. Specially for the latter one, I go used to tune the default naming, by looking at my cmake options and some library info (e.g. Boost version).<br>
><br>
> In the ctest script I use ctest_empty_binary_directory(), and I create a basic CMakeCache.txt to start the ctest_configure() afterwards. How can I read cmake options before ctest_start() (at this point I need BUILDNAME to be set!).<br>
><br></div></div></blockquote><div><br></div></div><div>You should set those variables in the ctest -S script. A ctest -S script is typically coupled to the specific machine and build that it represents, so it's the right place to set those variables.</div>
</div></blockquote><div><br></div><div><br></div></div><div>So, since the basic config option (e.g. compiler, in case I want to test more) has to be set in the ctest -S script, I can just use this info to generate the name from there?</div>
<div>In my case I would like to put some library version number in the BUILDNAME, in order to easily filter the results in the dashboard. Doing it in the ctest -S means invoking find_library(), i.e. perming the config in two different places.</div>
<span><font color="#888888">
<div><br></div><div><br></div><div>Michele</div></font></span></div>
</blockquote></div><div><br></div><br></div></div><div>Well, maybe you *should* do it in the CMakeLists then. You can't run find_library in a ctest -S script.</div><div><br></div>
</blockquote></div><br>