[Cmake] multiple choice option

[Andy Cedilnik]

Hi Klaas,

There is no multiple choice option right now. There are some ideas on
how to do it, but probably not before 2.0.

About wxWindows, I think it would be fairly easy for wxWindows people to
export all the necessary information in a file that can be then imported
in CMake. It does not have to be a CMake file. It could be just a simple
text file with all the options etc. That would benefit wxWindows people
too, because right now you have the same problem if you want to build
your own project with wxWindows.

				Andy

On Thu, 2003-10-23 at 10:40, Klaas Holwerda wrote:
> Is there a way to have a multiple choice option in Cmake(SetUp)? Like
> choosing from a list of  several possibilities, where this lis can be
> generated on the fly ( list of existing directories are whatever) by
> Cmake. Why,  i try to explain down here, but essential it is to let
> the user  choose a specific setup of a wxWindows library version. For
> wxWindows the number of configurations ( unicode/debug/dll etc etc.)
> can be almost endless, this because every change in its setup.h leads
> to a new unique library. The library and setup.h file generated for
> each unique configuration are essential to generate a proper Vc
> project with cmake. Some special configurations lead to fixed named
> directories, by wxWindows its buyild system, but others can be named
> as the builder of that specific wxWindows library desires.
> 
> I can detect the "default configurations", but i would prefer to have
> a list of $WXWIN)/lib its subdirectories, and display them in Cmake as
> a multiple choice option. (if possible with special comments added, to
> explain what is likely in each library configuration).
> So if this is possible, one of the generated wxWindows library
> configuration can simply be choosen by the user. After that Cmake will
> only create a project file/makefiles for that specific configuration.

> Combining every type of unique configuration inside one VC project
> file, i find a bad solution. ( debug/release/dll makes still sence,
> but for all possible configuration it makes no sence). Especially when
> looking from how Cmake works in case of makefiles. One should be able
> to generate makefiles and/or project files for any specific setup of
> library/libraries.

> If the above is wrong thinking ;-), advice is appreciated.