Re: [CMake] Building linux kernel module with Cmake

2007-11-04 Thread Suhas Jain
Hi, I have made changes to my CMakeLists.txt file Here is my complete CMakeLists.txt file >>>.. Set( KERNEL_DIR "/lib/modules/${CMAKE_SYSTEM_VERSION}/build" ) Set( kbuild_cmd ${CMAKE_MAKE_PROGRAM} -C ${KERNEL_DIR}

[CMake] FindXXX.cmake conventions

2007-11-04 Thread Joe
Hi, we have started to migrate the build system of our software to cmake. After a great success in starting the new build system some questions arise, when thinking about mid and long term maintainability. When writing own FindXXX.cmake modules, it seems to be of advantage to follow the same conve

Re: [CMake] lexical scoping

2007-11-04 Thread Philip Lowman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Neundorf wrote: > On Sunday 04 November 2007, Philip Lowman wrote: >> Brandon Van Every wrote: >>> And strongly consider SETLOCAL, SET_LOCAL, SET_CACHE or whatever. >> Absolutely. Here's what I would recommend... >> >> SET() should always se

Re: [CMake] Configuring for MSVC

2007-11-04 Thread David Cole
> > Is there any support for checking that the set of runtime libraries to > > be used is consistent? Specifically, can I scan the linker directives > > in prebuilt static libraries? > > I'm not sure what you're asking here. > > Prebuilt static libraries don't store linker directives. Yes, somet

Re: [CMake] lexical scoping

2007-11-04 Thread Hendrik Sattler
Am Sonntag 04 November 2007 schrieb Alexander Neundorf: > On Sunday 04 November 2007, Philip Lowman wrote: > > Brandon Van Every wrote: > > > And strongly consider SETLOCAL, SET_LOCAL, SET_CACHE or whatever. > > > > Absolutely. Here's what I would recommend... > > > > SET() should always set a glo

Re: [CMake] lexical scoping

2007-11-04 Thread Alexander Neundorf
On Sunday 04 November 2007, Philip Lowman wrote: > Brandon Van Every wrote: > > And strongly consider SETLOCAL, SET_LOCAL, SET_CACHE or whatever. > > Absolutely. Here's what I would recommend... > > SET() should always set a global variable to maintain complete backwards > compatibility. SETCACHE

Re: [CMake] lexical scoping

2007-11-04 Thread Philip Lowman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brandon Van Every wrote: > And strongly consider SETLOCAL, SET_LOCAL, SET_CACHE or whatever. Absolutely. Here's what I would recommend... SET() should always set a global variable to maintain complete backwards compatibility. SETCACHE() could be ad

Re: [CMake] Configuring for MSVC

2007-11-04 Thread Philip Lowman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Sharpless wrote: > What is the best way to ensure that release and debug targets get the > appropriate link libraries? Does cmake have a policy for this? TARGET_LINK_LIBRARIES allows you to specify an optional "debug" or "optimized" argument w

Re: [CMake] lexical scoping

2007-11-04 Thread Brandon Van Every
On Nov 4, 2007 5:10 AM, Alexander Neundorf <[EMAIL PROTECTED]> wrote: > On Saturday 03 November 2007, Bill Hoffman wrote: > > David Cole wrote: > > > After all the discussion / suggestions that have been part of this > > > thread, I like the following best: > > > > > > local(scope_name) > > > set

Re: [CMake] lexical scoping

2007-11-04 Thread Alexander Neundorf
On Saturday 03 November 2007, Bill Hoffman wrote: > David Cole wrote: > > After all the discussion / suggestions that have been part of this > > thread, I like the following best: > > > > local(scope_name) > > set(var1 "value1") > > set(var2 "value2") > > endlocal(scope_name) > > I would prefer