[Ctk-developers] Feedback - CTK_BUILD_ALL option

[Marco Nolden]

I like the idea. We have something similar in the MITK build system and 
we do not "force" all options to ON when enabling BUILD_ALL but we 
always check

IF(BUILD_Something OR BUILD_ALL)

This keeps the old configuration of libs. One use-case we have for that 
is the local pre-commit check. You change some interface in a class, 
turn on BUILD_ALL, check that everything builds and tests and after your 
commit you can turn it off again and have your old config.

Marco


On 10/22/2010 06:36 PM, Jean-Christophe Fillion-Robin wrote:
> Hi Folks,
>
> I propose to add the advanced CMake option named CTK_BUILD_ALL.
>
> By turning this option ON, a dashboard script could optionnally build
> all libraries, plugins and applications.
>
> I would like your comments regarding the following points:
>   1) Does the option name seems appropriate. Would CTK_ENABLE_ALL be
> better ? Or ...
>   2) Would it make sens to have that option showing up as a regular
> option ? (not an advanced one)
>   3) Would it be interesting to have also CTK_BUILD_ALL_LIBRARIES,
> CTK_BUILD_ALL_PLUGINS, CTK_BUILD_ALL_APPS ?
>   4) Do you think of any other use case beside of the Dashboard script
> one ?
>
> I published the following topic branch:
> http://github.com/jcfr/CTK/tree/add-build-all-cmake-option
>
> Thks
> Jc
>
> --
> Phone: 1-518-836-2174
> Ext: 304


-- 
----------------------------------------------------------------------
Dipl.-Inform. Med. Marco Nolden
Deutsches Krebsforschungszentrum       (German Cancer Research Center)
Div. Medical & Biological Informatics          Tel: (+49) 6221-42 2325
Im Neuenheimer Feld 280                        Fax: (+49) 6221-42 2345
D-69120 Heidelberg                             eMail: M.Nolden at dkfz.de