[Insight-developers] Additional CMake targets
Miller, James V (Research)
millerjv at crd . ge . com
Tue, 15 Jul 2003 07:54:30 -0400
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C34AC6.C59D3DDE
Content-Type: text/plain;
charset="iso-8859-1"
I think at the Philadelphia meeting we discussed adding a few additional
build targets to Insight. Since DevStudio and .NET show dozens of projects
it can be daunting to a new user to figure out what to build when. Also, I
find when I am making changes to the system, I just want to build the tests
and once I get things ironed out, I'll move onto the examples, etc.
We currently have an ALL_BUILD target, I think we discussed adding
ALL_LIBRARIES
ALL_TESTS
ALL_EXAMPLES
ALL_WRAPPERS (should this be broken down further into ALL_TCL_WRAPPERS,
ALL_PYTHON_WRAPPERS, etc?)
How should this be managed? Should we hand code these in the CMakeLists.txt
files? CMake should already know what all the libraries are so it could
build that one automatically (with the appropriate changes to CMake). While
CMake knows the names of the executables that it makes, it probably cannot
distinguish an executable that is a test from an executable that is an
example. So perhaps these targets should be spelled out in the
CMakeLists.txt files. However, this may become a maintenance issue (when
someone adds an example, they would have to remember to edit the
ALL_EXAMPLES target).
Jim
Jim Miller
_____________________________________
Visualization & Computer Vision
GE Research
Bldg. KW, Room C218B
P.O. Box 8, Schenectady NY 12301
millerjv at research . ge . com <mailto:millerjv at research . ge . com>
james . miller at research . ge . com
(518) 387-4005, Dial Comm: 8*833-4005,
Cell: (518) 505-7065, Fax: (518) 387-6981
------_=_NextPart_001_01C34AC6.C59D3DDE
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1141" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=418474611-15072003><FONT size=2>I think at the Philadelphia
meeting we discussed adding a few additional build targets to Insight.
Since DevStudio and .NET show dozens of projects it can be daunting to a new
user to figure out what to build when. Also, I find when I am making
changes to the system, I just want to build the tests and once I get things
ironed out, I'll move onto the examples, etc.</FONT></SPAN></DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2>We currently have an ALL_BUILD
target, I think we discussed adding</FONT></SPAN></DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=418474611-15072003><FONT
size=2>ALL_LIBRARIES</FONT></SPAN></DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2>ALL_TESTS</FONT></SPAN></DIV>
<DIV><SPAN class=418474611-15072003><FONT
size=2>ALL_EXAMPLES</FONT></SPAN></DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2>ALL_WRAPPERS (should this
be broken down further into ALL_TCL_WRAPPERS, ALL_PYTHON_WRAPPERS,
etc?)</FONT></SPAN></DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2>How should this be
managed? Should we hand code these in the CMakeLists.txt files? CMake
should already know what all the libraries are so it could build that one
automatically (with the appropriate changes to CMake). While CMake knows
the names of the executables that it makes, it probably cannot distinguish an
executable that is a test from an executable that is an example. So
perhaps these targets should be spelled out in the CMakeLists.txt files.
However, this may become a maintenance issue (when someone adds an example, they
would have to remember to edit the ALL_EXAMPLES target).</FONT></SPAN></DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=418474611-15072003><FONT size=2>Jim</FONT></SPAN></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV>
<P style="MARGIN: 0in 0in 0pt"><B><SPAN
style="COLOR: navy; FONT-FAMILY: 'Comic Sans MS'">Jim Miller</SPAN></B>
<BR><B><I><SPAN
style="FONT-SIZE: 10pt; COLOR: red; FONT-FAMILY: Arial">_____________________________________</SPAN></I></B><BR><EM><SPAN
style="FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: Arial">Visualization &
Computer Vision</SPAN></EM><I><SPAN
style="FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: Arial"><BR><EM>GE
Research</EM><BR><EM>Bldg. KW, Room C218B</EM><BR><EM>P.O. Box 8, Schenectady NY
12301</EM><BR><BR></SPAN></I><EM><U><SPAN
style="FONT-SIZE: 7.5pt; COLOR: blue"><A
href="mailto:millerjv at research . ge . com">millerjv at research . ge . com</A></SPAN></U></EM></P>
<P style="MARGIN: 0in 0in 0pt"><EM><U><SPAN
style="FONT-SIZE: 7.5pt; COLOR: blue">james . miller at research . ge . com</SPAN></U></EM><BR><I><SPAN
style="FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: Arial">(518) 387-4005, Dial
Comm: 8*833-4005, </SPAN></I><BR><I><SPAN
style="FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: Arial">Cell: (518) 505-7065,
Fax: (518) 387-6981</SPAN></I> </P></DIV>
<DIV> </DIV></BODY></HTML>
------_=_NextPart_001_01C34AC6.C59D3DDE--