Re: [CMake] configuration input to cmake

2007-05-14 Thread Guilherme Balena Versiani
Hello Jun Sun, I hope now I understood your question. First, let compare auto-tools to cmake: the three main steps involved in building the system are about the same (though the cmake seems to use a better cache system than 'configure' and it generates a something optimized set of GNU Makefil

Re: [CMake] configuration input to cmake

2007-05-14 Thread Jun Sun
Thanks for the pointers. It makes a lot of sense to me. Jun On Sat, May 12, 2007 at 10:09:15AM +0200, Eric Noulard wrote: > 2007/5/12, Jun Sun <[EMAIL PROTECTED]>: > >On Fri, May 11, 2007 at 01:38:26PM -0400, Bill Hoffman wrote: > >> Guilherme Balena Versiani wrote: > >> > > >> > > >> >Jun Sun e

Re: [CMake] configuration input to cmake

2007-05-12 Thread Eric Noulard
2007/5/12, Jun Sun <[EMAIL PROTECTED]>: On Fri, May 11, 2007 at 01:38:26PM -0400, Bill Hoffman wrote: > Guilherme Balena Versiani wrote: > > > > > >Jun Sun escreveu: > >>My build process involves a configuration stage. It roughly looks like > >>this: > >> > >>* Generate cmakefile.inc and config.h

Re: [CMake] configuration input to cmake

2007-05-11 Thread Jun Sun
On Fri, May 11, 2007 at 01:38:26PM -0400, Bill Hoffman wrote: > Guilherme Balena Versiani wrote: > > > > > >Jun Sun escreveu: > >>My build process involves a configuration stage. It roughly looks like > >>this: > >> > >>* Generate cmakefile.inc and config.h from .config file > You may also want to

Re: [CMake] configuration input to cmake

2007-05-11 Thread 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 conf

Re: [CMake] configuration input to cmake

2007-05-11 Thread Bill Hoffman
Guilherme Balena Versiani wrote: Jun Sun escreveu: My build process involves a configuration stage. It roughly looks like this: * Generate cmakefile.inc and config.h from .config file You may also want to look at the configure_file command. -Bill ___

Re: [CMake] configuration input to cmake

2007-05-11 Thread Guilherme Balena Versiani
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 # cmake ../ 2) build software: # make Optionally, you can have a 'make install' (see INST

[CMake] configuration input to cmake

2007-05-11 Thread Jun Sun
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