Does the same happen using the loadable module template [1] ?

[1] https://github.com/Slicer/Slicer/tree/master/Extensions/Testing/LoadableExtensionTemplate

I've just verified that this bug also occurs with the simple loadable module template (with the changes required to CMakeLists.txt to build it outside of the Slicer source).

From Steve:

To help debug this, can you the following steps and then describe how what you are doing differs?

If I cut-and-paste this code [1] that creates a dummy extension it builds and loads correctly. If I cd to the build directory and run "cmake ." and make I don't get any errors or warnings. What do you get?

Best,
Steve

[1] http://slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/ModuleWizard#Creating_and_Testing_a_Loadable_Module

From Luis:

Hi Steve,

I should have been clearer: I have an extension with a few modules, and I'm trying to individually build one specific module from that extension. Here are the steps I took to reproduce the bug:

NEWMODULE=NewModule
SLICERSUPERBUILD=pwd

../Slicer/Utilities/Scripts/ModuleWizard.py --template ../Slicer/Extensions/Testing/LoadableExtensionTemplate --target /tmp/${NEWMODULE} ${NEWMODULE}
mkdir /tmp/${NEWMODULE}-build

then I added the changes from [1] to /tmp/${NEWMODULE}/LoadableModuleTemplate/CMakeLists.txt. Note: I had to add a project() line to make it work, unlike what is specified in the documentation (J-C and I spoke about this). Next:

cd /tmp/${NEWMODULE}-build
cmake /tmp/${NEWMODULE}/LoadableModuleTemplate -DSlicer_DIR:PATH=${SLICERSUPERBUILD}/Slicer-build

Please note that I call cmake on the module within the extension, not the extension itself. This is so I can work with one module at a time. At this point, the build configures just fine.

Next, I make any arbitrary change at all to the source configuration. For instance, I added a message() call to /tmp/${NEWMODULE}/LoadableModuleTemplate/CMakeLists.txt. When I return to /tmp/${NEWMODULE}-build and run "cmake .", the bug occurs.

Thanks for your help!

-Luis

[1] http://slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Tutorials/BundleModulesIntoExtension#Possible_tweak_of_Module_level_CMakeLists.txt

From mailing list:

Hi Steve,

I've attached the edited file for NewModule/LoadableModuleTemplate/CMakeLists.txt that I use to reproduce the error. The lines marked "new" are the ones not present in the template. Once the module is configured, you can simply uncomment the message() call near the top and run "cmake ." again to see the error. I've also attached some of the errors output (I couldn't go far enough in my command line history to get the entire error).

To repeat the steps:

1) Create the template extension+module structures as done above.
2) Replace NewModule/LoadableModuleTemplate/CMakeLists.txt with the file I've attached.
3) mkdir /tmp/NewModule-build; cd /tmp/NewModule-build
4) cmake -DSlicer_DIR:PATH=/path/to/Slicer-build /tmp/NewModule/LoadableModuleTemplate
5) Uncomment the message() line in /NewModuleLoadableModuleTemplate/CMakeLists.txt
6) cd /tmp/NewModule-build; cmake .

Let me know if you have any more questions!

Note: CMakeLists.txt has been attached to bug report

From mailing list:

To update:

JC and I localized the problem to be with the following line:

find_package(Slicer COMPONENTS ConfigurePrerequisites)

When that line is commented out, re-configuration works perfectly.

Hi Luis,

I had an other look at the issue and fail to reproduce it. Is this still a problem ?

This has already been fixed in r22115
See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=22115

See also r22349 - http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=22349

Closing resolved issues that have not been updated in more than 3 months

Just confirming that this has indeed been fixed.

Thanks for checking :)