After investigation and guidance from Matt McCormick & Bill Lorensen here is the deal:
If your Remote module does NOT contain a source directory with a CMakelists.txt, it will work if you run CMake twice -- once to download the remote source, and a second time for the Module infrastructure to recognize the remote module after download. That much makes sense. What doesn't make sense to me is that if you DO have a 'src' directory and build a target (e.g. a library) then it seems as though you don't need that second CMake run. Which, now that I understand the process makes no sense to me. Which just goes to show: All software systems will eventually rise to a level of complexity where they are capable of baffling and surprising their programmers. -- Kent Williams [email protected] ________________________________ 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. ________________________________ _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Kitware offers ITK Training Courses, for more information visit: http://kitware.com/products/protraining.php Please keep messages on-topic and check the ITK FAQ at: http://www.itk.org/Wiki/ITK_FAQ Follow this link to subscribe/unsubscribe: http://www.itk.org/mailman/listinfo/insight-developers
