On Mon, May 18, 2009 at 3:50 PM, Brad King <span dir="ltr">&lt;<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Michael Jackson wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
  thanks for the heads up about vxl. I took those 2 scripts and adapted them for boost. I have since been able to submit an experimental Dashboard to &lt;<a href="http://www.cdash.org/CDashPublic/index.php?project=Boost" target="_blank">http://www.cdash.org/CDashPublic/index.php?project=Boost</a>&gt;. Look for <a href="mailto:ferb@bluequartz.net" target="_blank">ferb@bluequartz.net</a> - the one that actually ran all the tests.<br>

</blockquote>
<br></div>
Nice.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Also, if you click on the &quot;site&quot; you get some stats about the machine that built boost.. All of which is either wrong or not filled in. Are there some configuration options for this that need to be set or is the parsing code for CTest not grepping OS X machines correctly?<br>

</blockquote>
<br></div>
IIRC it&#39;s parsed by code in the &quot;Source/kwsys/SystemInformation.cxx&quot;<br>
source in CMake:<br>
<br>
<a href="http://www.cmake.org/cgi-bin/viewcvs.cgi/Source/kwsys/SystemInformation.cxx?revision=1.40&amp;root=CMake&amp;view=markup" target="_blank">http://www.cmake.org/cgi-bin/viewcvs.cgi/Source/kwsys/SystemInformation.cxx?revision=1.40&amp;root=CMake&amp;view=markup</a><br>

<br>
</blockquote></div><br>I looked at this issue briefly a couple months ago, but was too busy to make a ctest fix at the time. The problem with SystemInformation on Mac OSX is that the command lines used to gather the information do not use a full path to execute the programs. We should do a FIND_PROGRAM equivalent and use the full path to the programs because the environment of running from a crontab entry does not have the same PATH setup that a typical Mac terminal shell does...<br>
<br>I just opened a cmake/ctest bug and assigned it to myself so it does not get lost in the shuffle...<br><a href="http://public.kitware.com/Bug/view.php?id=9050">http://public.kitware.com/Bug/view.php?id=9050</a><br><br>
HTH,<br>David<br><br>