Hi Matt,
Actually, none of your variations use the correct syntax. Have a look at
my example in the previous mail. The format must be a valid CMake cache
file, which is supplied when cmake is called to configure MITK (during
MITK's superbuild process), which is
cmake -C ${MITK_INITIAL_CACHE_FILE} -D ...
On 08/09/2011 06:15 PM, Clarkson, Matt wrote:
Hi Sascha, i have tried:
...
In SuperBuild.cmake, the initial args are used like this:
CMAKE_ARGS
${mitk_initial_cache_arg}
and from the CMake manual, this section is for command line args. So,
is this variable being used in the right place?
Yes, the command line will be cmake -C initial_cache_file_name ...
Also, in Modules/Bundles/PluginList.cmake there is a list of plugins
to turn on.
Whereas in Modules/Bundles/CMakeLists.txt is a list of plugins in the
PLUGIN_EXCLUDE_LIST.
Which is actually being used?
The MITK build system still supports legacy BlueBerry bundles and CTK
plugins simultaneously. PluginList.cmake contains the default build
options for CTK plugins. The BlueBerry bundle build system automatically
tries to "discover" available bundles so we prevent it from
"discovering" bundles which are actually CTK plugins by adding their
names to the PLUGIN_EXCLUDE_LIST.
Also, when I set things in the file PluginList.cmake manually, it
seems to turn plugins on, but then, what does the PLUGIN_EXCLUDE_LIST do?
I hope the above comment explains this one as well.
Best,
Sascha
------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
