Hi Thomas,
I just built MITK with superbuild OFF and had no problems.
For the file MITK/Utilities/CMakeLists.txt the CMake variables
PROJECT_BINARY_DIR and CMAKE_BINARY_DIR point to the same directory.
Are you calling MITK's top-level CMakeLists.txt via include() or
add_subdirectory() from one of your own project's CMake files, by any
chance?
Best,
Sascha
On 09/16/2011 01:37 PM, Thomas Wolf wrote:
>> Actually, only mbilogConfig ends up at a different place...
> In MITK/Utilities/CMakeslist:
> SET(mbilog_CONFIG_FILE
> "${PROJECT_BINARY_DIR}/${MODULES_CONF_DIRNAME}/mbilogConfig.cmake" CACHE
> INTERNAL "Path to module config" FORCE)
>
> points to ${PROJECT_BINARY_DIR} instead of pointing to
> ${CMAKE_BINARY_DIR} as in mitkMacroCeateModuleConf.
>
> Please correct this.
>
> 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
------------------------------------------------------------------------------
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
