[Insight-developers] Buildflags for producing flaky executabl es

[Lorensen, William E (Research)]

I just modified the SystemInformationTest so that is creates a BuildName.xml file. It should roll up
Nightly. We'll see in the morning...

Bill

-----Original Message-----
From: Brad King [mailto:brad.king@kitware.com]
Sent: Tuesday, March 04, 2003 12:35 PM
To: hans-johnson@uiowa.edu
Cc: Insight Developers
Subject: Re: [Insight-developers] Buildflags for producing flaky
executables


> The itkSystemInformationTest that you added is VERY useful.  The only
> problem that I see is that it is buried in a non-intuitive place.  In
> addition, only the developers who read yesterdays message addressed to
> me would know that this information exists.
[snip]
> I think that this information should also be available on the main
> testing page.  For example, if you were to click on the buildname, then
> that would take you directly to this set of information.  I thought that
> this was what the cfg field of the dashboard was for (by the way, what
> is the current cfg information useful for?).

The cfg column is the output of the run of CMake to create/update the ITK
build tree.

As far as placement of the system information, look at the following
build on the ITK page:

  hythloth.kitware Linux-gcc321

Note the tag next to the build name.  It is a link to a note attached to
that build.  We could probably update the system information test to add
such a note that contains the build flags and perhaps a link to the rest
of the test's output.

-Brad

_______________________________________________
Insight-developers mailing list
Insight-developers@public.kitware.com
http://public.kitware.com/mailman/listinfo/insight-developers