<div class="gmail_quote">On Fri, Aug 24, 2012 at 9:34 AM, Leif Walsh <span dir="ltr"><<a href="mailto:leif.walsh@gmail.com" target="_blank">leif.walsh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF"><div>They are generated from facts I detect about the os<br><br></div></div></blockquote><div><br></div><div>Ah .... ok. Better then. :-)</div><div><br></div><div>You could do the same thing in a ctest script. A lot of the projects we work on at Kitware share a "common" script for the project that is included by all the dashboard scripts that run. You could put general code into one of them, too, but since it's common for people to want to customize these variables on a per-submission basis, we typically just require them to be set in the wrapper scripts that are machine-specific.</div>
<div><br></div><div>Cheers,</div><div>David</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF"><div>
Sent from my iPhone</div><div><div class="h5"><div><br>On Aug 24, 2012, at 9:24, David Cole <<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>> wrote:<br><br></div><div></div><blockquote type="cite">
<div><br><br><div class="gmail_quote">On Fri, Aug 24, 2012 at 9:07 AM, Leif Walsh <span dir="ltr"><<a href="mailto:leif.walsh@gmail.com" target="_blank">leif.walsh@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I set the build name and site in my CMakeLists.txt before calling include(CTest) and it works.<br>
<br></blockquote><div><br></div><div>But then you can only submit dashboards from one site with that CMakeLists file...? Anybody else submitting a dashboard for your project will pick up the same site and build names.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sent from my iPhone<br>
<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>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><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
><br>
> Thanks a lot,<br>
> Michele<br>
><br>
</div></div>> --<br>
><br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
--<br>
<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div><br>
</div></blockquote></div></div></div></blockquote></div><br>