<div dir="ltr">The double cmake makes sense to me. The first fetches the remote module, the second turns it on. If you run the cmake GUI, I think you would do the double cmake naturally.<div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, Jun 21, 2013 at 5:36 PM, Williams, Norman K <span dir="ltr"><<a href="mailto:norman-k-williams@uiowa.edu" target="_blank">norman-k-williams@uiowa.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
After investigation and guidance from Matt McCormick & Bill Lorensen here<br>
is the deal:<br>
<br>
If your Remote module does NOT contain a source directory with a<br>
CMakelists.txt, it will work if you run CMake twice -- once to download<br>
the remote source, and a second time for the Module infrastructure to<br>
recognize the remote module after download.<br>
<br>
That much makes sense. What doesn't make sense to me is that if you DO<br>
have a 'src' directory and build a target (e.g. a library) then it seems<br>
as though you don't need that second CMake run. Which, now that I<br>
understand the process makes no sense to me.<br>
<br>
Which just goes to show: All software systems will eventually rise to a<br>
level of complexity where they are capable of baffling and surprising<br>
their programmers.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Kent Williams <a href="mailto:norman-k-williams@uiowa.edu">norman-k-williams@uiowa.edu</a><br>
<br>
<br>
<br>
________________________________<br>
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.<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<br>
<a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Kitware offers ITK Training Courses, for more information visit:<br>
<a href="http://kitware.com/products/protraining.php" target="_blank">http://kitware.com/products/protraining.php</a><br>
<br>
Please keep messages on-topic and check the ITK FAQ at:<br>
<a href="http://www.itk.org/Wiki/ITK_FAQ" target="_blank">http://www.itk.org/Wiki/ITK_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.itk.org/mailman/listinfo/insight-developers" target="_blank">http://www.itk.org/mailman/listinfo/insight-developers</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Unpaid intern in BillsBasement at noware dot com<br>
</div>