Re: [CMake] Add configuration support to include_directories()

Bill Hoffman a écrit : Robert Dailey wrote: For debug: C:\foo\bar-d For release: C:\foo\bar Note that the text "Debug" or "Release" is not used in the include path, so simply using CFG_INTDIR would not work I don't think (Unless I'm missing something again). This is why in CMake I need to do

Re: [CMake] Add configuration support to include_directories()

Philip Lowman a écrit : On Mon, Dec 22, 2008 at 11:27 PM, Robert Dailey > wrote: On Mon, Dec 22, 2008 at 9:23 PM, Bill Hoffman mailto:bill.hoff...@kitware.com>> wrote: Investigate CMAKE_CFG_INTDIR. I believe for Visual Studio outp

Re: [CMake] InstallRequiredSystemLibraries with MSVC9 SP1

Bill Hoffman a écrit : cyril_wobow wrote: Hi everyone, I encountered an annoying problem when installing/packaging a project using the InstallRequiredSystemLibraries script under MSVC9 SP1. The following files are properly bundled next to my executable (in the "./bin" install

[CMake] InstallRequiredSystemLibraries with MSVC9 SP1

Hi everyone, I encountered an annoying problem when installing/packaging a project using the InstallRequiredSystemLibraries script under MSVC9 SP1. The following files are properly bundled next to my executable (in the "./bin" install directory), which is great : - Microsoft.VC90.CRT.manifes

Re: [CMake] source_group(): Which project is it added to?

Robert Dailey a écrit : On Mon, Dec 1, 2008 at 12:25 PM, cyril_wobow <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Robert Dailey a écrit : That is indeed how I would expect it to work, but that's not what is happening. Below is the actual CMake

Re: [CMake] source_group(): Which project is it added to?

Robert Dailey a écrit : On Mon, Dec 1, 2008 at 10:52 AM, cyril_wobow <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: It's my understanding that you are trying to declare two "solutions" p1 and p2 (using visual studio's terminology). The sourc

Re: [CMake] source_group(): Which project is it added to?

Robert Dailey a écrit : On Tue, Nov 25, 2008 at 1:39 PM, Robert Dailey <[EMAIL PROTECTED] > wrote: I'm having an issue right now where I'm trying to setup 2 projects in 1 CMakeLists.txt file. Basically what I do is: project( p1 ) add_executable()

Re: [CMake] Complaint about if..endif

Andreas Schneider a écrit : On Sunday 23 November 2008 17:43:53 cyril_wobow wrote: Sure, I guess we are all here because CMake is a very powerful suite, with tons of functionalities and useful abstractions. But I challenge anyone to seriously tell me that he/she enjoys writing CMake script

Re: [CMake] Complaint about if..endif

Robert Dailey a écrit : On Sun, Nov 23, 2008 at 4:20 AM, cyril_wobow <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: Like a ... python front end ? Seriously, cmake is really, really, really verbose and terribly unreadable as a scripting language... I would ag

Re: [CMake] Complaint about if..endif

Jack Andrews a écrit : hi rob, Why must endif() contain the same expression as the associated if() command? i think this could be the most noticed feature of cmake (in the five minute test). as noted, in other posts, you don't have to any more. but i've been thinking of creating anot

Re: [CMake] CMake problem on Solaris with suncc

Here is the environment I enforce on solaris to build with cmake/solaris/suncc64 : export LINKFLAGS="-m64" ; export CFLAGS="-m64" ; export CPPFLAGS="-m64"; export CC=/opt/SUNWspro/bin/suncc ; export CPP=/opt/SUNWspro/bin/suncc; export CXX=/opt/SUNWspro/bin/sunCC Hope this helps ! Cyril Ger

Re: [CMake] CMake 2.6.2 ignores my DEBUG_CONFIGURATIONS global property!

Nevermind, I've just understood that this feature is not part of 2.6.2. Guess I'll have to use the cvs branch until next release :| Cyril cyril_wobow a écrit : CMake 2.6.2 ignores my DEBUG_CONFIGURATIONS global property! After a quick step in cmake's code, it looks like the

[CMake] CMake 2.6.2 ignores my DEBUG_CONFIGURATIONS global property!

CMake 2.6.2 ignores my DEBUG_CONFIGURATIONS global property! After a quick step in cmake's code, it looks like the property falls into another cmPropertyMap object than the one where it is look for (they belong to two different cmake objects) Did I miss something ? Awesome work though! Cyril __

Re: [CMake] .RC files and Icon with Visual Studio

This works fine for me : ADD_EXECUTABLE(myexe resources/GeomAction2008.rc ... ) Joachim de Vries a écrit : CMake version 2.6-patch 0 Visual Studio 2005 Windows XP Hi, does anyone know how to add resource files to my visual studio project via cmake? I need it to

Re: [CMake] multi-line definitions

Have you tried the following SET (CMAKE_C_FLAGS_RELEASE "-mcpu=arm7tdmi" "-std=gnu99" "-fgnu89-inline" ... "-DNDEBUG") Cyril Emmanuel Blot a écrit : Hi, Is it possible to write variable definition directives using multiple lines, i.e. I have a long definition string such as: SET (CMAKE_C_

[CMake] cannot invoke project() from a separate cmake file

Hello I am confronted to the following problem: It seems that the PROJECT command cannot be invoked in a macro that is located in a cmake file that is included by my main CMakeLists.txt file. This issue has been encountered a few years ago: http://www.cmake.org/pipermail/cmake/2005-February/0

[CMake] Customizing target locations with VS generator

Hello I set the CMAKE_ARCHIVE_OUTPUT_DIRECTORY, CMAKE_LIBRARY_OUTPUT_DIRECTORY and CMAKE_RUNTIME_OUTPUT_DIRECTORY to, say, "${CMAKE_SOURCE_DIR}/bin" . I also set suffixes so any target in any build configuration has a unique name within my build tree. CMake's behavior with Visual Studio gen

Re: [CMake] custom configuration types and linking with 3rd-party libs

I must say I am pretty glad about that. Kind regards, Cyril Brad King a écrit : Philip Lowman wrote: Ultimately, TARGET_LINK_LIBRARIES() works just fine the way it is with the debug/optimized keywords satisfying normal use cases. The debug/optimized keywords are in the lexicon and they aren

Re: [CMake] custom configuration types and linking with 3rd-party libs

Yuri V. Timenkov a écrit : On Tuesday 26 August 2008 15:53:31 Philip Lowman wrote: On Mon, Aug 25, 2008 at 9:27 AM, cyril_wobow <[EMAIL PROTECTED]> wrote: Philip Lowman a écrit : Does LINK_INTERFACE_LIBRARIES_ do what you want to do? See http://www.cmake.org/HTML/cma

Re: [CMake] custom configuration types and linking with 3rd-party libs

Yuri V. Timenkov a écrit : On Monday 25 August 2008 16:28:52 cyril_wobow wrote: Thank you for your answer. Sorry not to have provided the patch as an attached file. No, its just more convenient to track issue history and patches. Indeed, it would be a nice functionality. In my

Re: [CMake] custom configuration types and linking with 3rd-party libs

Philip Lowman a écrit : On Mon, Aug 25, 2008 at 6:04 AM, Yuri V. Timenkov <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: On Monday 25 August 2008 13:04:56 cyril_wobow wrote: > Hi again, > > At the end of the present mail there is a dirty

Re: [CMake] custom configuration types and linking with 3rd-party libs

XCode like I do. Then, what about the same patch with a slightly different test? like matching the this->Config string against the following regexp: "^(DEBUG|(.+_DBG))$" Regards Cyril Yuri V. Timenkov a écrit : On Monday 25 August 2008 13:04:56 cyril_wobow wrote: Hi again,

Re: [CMake] custom configuration types and linking with 3rd-party libs

g && cmSystemTools::UpperCase(this->Config).find("DEBUG") != std::string::npos) Regards, Cyril cyril_wobow a écrit : Hi, I set my project's CMAKE_CONFIGURATION_TYPES variable with some custom configurations (e.g. GuiDebug, GuiRelease, ConsoleDebug, ConsoleRelease). Each of

[CMake] custom configuration types and linking with 3rd-party libs

Hi, I set my project's CMAKE_CONFIGURATION_TYPES variable with some custom configurations (e.g. GuiDebug, GuiRelease, ConsoleDebug, ConsoleRelease). Each of them have their own compilation flags, which is great, especially for visual studio users that don't want to bother with a config.h.in fi