<div>Kent,</div>
<div> </div>
<div>That macro is my doing. I'll take a look when I get back to ork on Friday. Maybe some other CMake guru and help in the meantime.</div>
<div> </div>
<div>Bill</div>
<div><br><br> </div>
<div><span class="gmail_quote">On 3/8/06, <b class="gmail_sendername">Kent Williams</b> <<a href="mailto:kent@psychiatry.uiowa.edu">kent@psychiatry.uiowa.edu</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I'm having trouble even determining which mailing list this should go to<br>-- insight-developers? insight-users? cmake-users?
<br><br>I'm going to try it here on insight-users first.<br><br>I am trying to build a number of packages all at once, controlled by a<br>toplevel CMakeLists.txt.<br><br>In other words I have a directory tree like this<br>
<br>src/<br> Insight<br> CableSwig<br> VTK<br> InsightApplications<br> WrapITK<br> SOViewer<br> KWWidgets<br><br>The top level directory (src) has this CMakeLists.txt file:<br><br>PROJECT(ITKVTKKWW)<br>ADD_SUBDIRECTORY(Insight )
<br>ADD_SUBDIRECTORY(CableSwig )<br>ADD_SUBDIRECTORY(VTK )<br>ADD_SUBDIRECTORY(InsightApplications )<br>ADD_SUBDIRECTORY(WrapITK )<br>ADD_SUBDIRECTORY(SOViewer )<br>ADD_SUBDIRECTORY(KWWidgets )<br><br>The problem is that Insight has a problem in one of its macros, which
<br>generates the following errors:<br><br>CMake Error: File<br>/scratch/kent/KWW/src/CMake/CheckCPPDirectiveExists.cxx.in does not exist.<br>CMake Error: Error in cmake code at<br>/scratch/kent/KWW/src/Insight/CMake/CheckCPPDirective.cmake:11:
<br>CONFIGURE_FILE Problem configuring file<br>CMake Error: Error in cmake code at<br>/scratch/kent/KWW/src/Insight/CMakeLists.txt:470: A command failed<br>during the invocation of macro "CHECK_CPP_DIRECTIVE_EXISTS".
<br>CMake Error: Error in cmake code at<br>/scratch/kent/KWW/src/Insight/CMakeLists.txt:470:<br>CHECK_CPP_DIRECTIVE_EXISTS unknown error.<br>The end of a CMakeLists file was reached with an IF statement that was<br>not closed properly.
<br>Within the directory: /scratch/kent/KWW/src/Insight<br><br>Now I understand (roughly) what the problem is. The<br>CHECK_CPP_DIRECTIVE_EXIST Macro uses a helper file<br><a href="http://CheckCPPDirectiveExists.cxx.in">CheckCPPDirectiveExists.cxx.in
</a>, which is in Insight/CMake. If you<br>configure Insight by itself, it can find this file relative to<br>${CMAKE_SOURCE_DIR}, because that will resolve to the Insight source tree.<br>But if, as I have done, you want to get Insight built as part of a large
<br>project, you lose; ${CMAKE_SOURCE_DIR} is the parent directory -- in my<br>case src.<br><br>Does this mean you _MUST ALWAYS_ configure, build and install Insight by<br>itself? This seems kind of counterproductive for a couple of reasons:
<br><br>1. If you can plug Insight into a larger project, you can encapsulate<br>the configuration information to produce compatible versions of<br>different compenent libraries.<br>2. It doesn't seem a large price to pay to make Insight buildable in
<br>more than one context.<br><br><br>_______________________________________________<br>Insight-users mailing list<br><a href="mailto:Insight-users@itk.org">Insight-users@itk.org</a><br><a href="http://www.itk.org/mailman/listinfo/insight-users">
http://www.itk.org/mailman/listinfo/insight-users</a><br></blockquote></div><br>