> Hi,
> 
> this also happens to the Non-superbuild. I end up with several
> moduleConf folders which files in return cannot be found by MITK while
> building itself.
> 
> Sources are origin/master as of 15.09.2011.
> 
> Regards,
> Thomas

Still debugging:

As an update, i see the line:
SET(${MODULE_NAME}_CONFIG_FILE
"${CMAKE_BINARY_DIR}/${MODULES_CONF_DIRNAME}/${MODULE_NAME}Config.cmake"
CACHE INTERNAL "Path to module config" FORCE)
in the MITK_CREATE_MODULE_CONF.cmake file.

the location "${CMAKE_BINARY_DIR}/${MODULES_CONF_DIRNAME} sems to be
wrong, because apprently no files in it will be found. Sadly, almost all
module configs are created there.

Regards,
Thomas

------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to