Minimize confusion associated with buildsystem

[commontk]

Minimize confusion associated with buildsystem

[saschazelzer]

For CTK, we could check for the file CTK-build/build_options.cmake (for example).

During superbuild, if the file does not exist, we use default value (or the current cache values) for the CTK_[APP|LIB|PLUGIN]_* variables.

When configuring the "real" project (the CTK-build dir), we generate the contents for CTK-build/build_options.cmake containing "set(CTK_* ... CACHE FORCE)" statements.

During superbuild configure-time, if the file exists, we just read it in.

Could that work?

[jcfr]

Good idea

Within CTK-build, instead of creating an other file (build_options.cmake), the superbuild system could just extract the value within CTK-build/CMakeCache.cmake using regular expression.

This could be done by adding a macro name SUPERBUILD_OPTION() that could be used instead of OPTION()

[saschazelzer]

Yes, I thought about that too. I think my only concern back then was speed, especially under Windows. I love how fast the superbuild configure step is. Parsing the CMakeCache.txt file potentially a lot of times maybe slow - but maybe not (we should try it out). It would certainly be more elegant.

[jcfr]

Closing this issue since it not been updated in the past 3 years.