[CMake] configuration input to cmake

[Jun Sun]

Thanks for the pointer. But I was referring to the configuration
for the cmake itself. For example, one build may include module A
and another build may not include module B instead.

Now thing about it, what is the recommanded way of achieving this goal?

I can thinking of two ways:

1. Pass config options to cmake itself so that it generates two
   different make systems that does two things

2. Somehow generate just one make system but the make system itself takes
   an input argument that dictates which way to do the build.

Which one is better in cmake world? I was thinking about 1).

Thanks.

Jun

On Fri, May 11, 2007 at 02:22:46PM -0300, Guilherme Balena Versiani wrote:
> AFAIK using cmake involves basically two steps:
> 
> 1) something like configure & generate build files (GNU Makefile, MSVC, 
> KDevelop3, XCode, etc). For a tipical 'out-of-source' building:
> 
>    # mkdir <build_dir>
>    # cmake ../<source_dir>
> 
> 2) build software:
> 
>    # make
> 
> Optionally, you can have a 'make install' (see INSTALL command), a 'make 
> package' (which means you are using CPack) and 'make test' (see CTest).
> 
> Regards,
> 
> Guilherme Balena Versiani.
> 
> 
> Jun Sun escreveu:
> >My build process involves a configuration stage. It roughly looks like
> >this:
> >
> >* Generate cmakefile.inc and config.h from .config file
> >* Use cmake to generate solution files or makefiles
> >* Build with native toolchain
> >
> >It is not clear to me whether I should use an external script to do 
> >step 1 or I can even do the first step with cmake itself.
> >
> >I am very new to cmake. Sorry if this is a dumb question. :)
> >
> >Cheers.
> >
> >Jun
> >_______________________________________________
> >CMake mailing list
> >CMake at cmake.org
> >http://www.cmake.org/mailman/listinfo/cmake