At the moment the BuildConfiguration functionality could only be used by adding files to the MITK source code. The mitkFunctionEnableBuildConfiguration.cmake file just looks in the mitk CMake/BuildConfigurations folder. It would be nice if external users can create their own build configuration by adding an additional/external path to have a look for config files.
Description
Description
Event Timeline
Comment Actions
There are two possibilities:
- External projects define own build configuration for their project
or/and
- External projects define own build configuration for MITK
Comment Actions
Now the cmake mitkFunctionBuildConfigurations.cmake can handle internal and external folder (users choice) to get the build config files. (personal branch)
Problems:
- How can we set some mitk build (not superbuild) cmake configs from an external build configuration file
@Stefan: My cmake "know how" ends here. Can you please have a look on that?
Comment Actions
One practical approach could be to try to iterate in the MITK-superbuild over all cache variables that begin with "MITK_BUILD_org.mitk." and pass them to MITK as CACHE_ARGS.
Comment Actions
Hi there! 🙂
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑
Best wishes,
The MITK devs