[CMake] cannot generate safe linker path warning

On OS X I am getting an endless stream of warnings like this: CMake Warning at /Users/boudewijn/src/kde/ins/share/apps/cmake/modules/KDE4Macros.cmake:570 (add_library): Cannot generate a safe linker search path for target kodocinfopropspage because files in some directories may conflict

[CMake] How to call specific tools between preprocessing and compilation steps ?

Hi, I am a recent user of CMake. I want to use specific tools between preprocessing and compilation steps in order to instrument code and get structural coverage : (C files -- preprocessing -- instrumentation -- coverage -- compilation). Both steps instrumentation and coverage are done by

[CMake] Updated: CMake 2.6.2-1

CMake CMake 2.6.2-1 is now available on Cygwin mirrors. There has been a new release of the official cmake (2.6.2-1). This is a minor release from 2.6.0 to 2.6.2 Changes in CMake 2.6.2 RC 6 - Fix bug#7669 cpack did not work when sym-linked after install Changes in CMake 2.6.2 RC 5 - Add beta

[CMake] NMake problems when upgrading to CMake 2.6.2

Our software team is having problems upgrading to CMake 2.6.2 from our current working build system that uses CMake 2.4.7. In particular, we are using the Visual Studio 7 .NET 2003, NMake Makefiles, Unix Makefiles, and CodeBlocks - Unix Makefiles project/makefile generators. The first problem

[CMake] MSVC71 problems when upgrading to CMake 2.6.2

Our software team is having problems upgrading to CMake 2.6.2 from our current working build system that uses CMake 2.4.7. In particular, we are using the Visual Studio 7 .NET 2003, NMake Makefiles, Unix Makefiles, and CodeBlocks - Unix Makefiles project/makefile generators. We are having a

Re: [CMake] NMake problems when upgrading to CMake 2.6.2

From your same command prompt that you ran cmake in (at N:\dsci\repo\WMI\trunk\wxWMI\src\nmake) what is the output of: cl where cl echo %PATH% ? On Thu, Oct 9, 2008 at 11:51 AM, Luke Kucalaba [EMAIL PROTECTED] wrote: Our software team is having problems upgrading to CMake 2.6.2 from

Re: [CMake] NMake problems when upgrading to CMake 2.6.2

Thanks David for the quick response. Sorry I was having problems with message size, so I couldn't attach the files I wanted to originally. I'll inline the vctoolkit.bat file here, which is a small DOS script we use to setup the MSVC71 toolkit environment: @echo off if

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Luke Kucalaba wrote: Our software team is having problems upgrading to CMake 2.6.2 from our current working build system that uses CMake 2.4.7. In particular, we are using the Visual Studio 7 .NET 2003, NMake Makefiles, Unix Makefiles, and CodeBlocks - Unix Makefiles project/makefile

[CMake] Object files: .o vs .obj?

With (allegedly) identical CMake setups, we have two machines that generate different outputs: .o vs. obj. The one that generates .obj has Visual Studio installed, the other doesn't. I tried adding SET(CMAKE_C_OUTPUT_EXTENSION .obj) to my Toolchain file, but it made no difference. The

Re: [CMake] NMake problems when upgrading to CMake 2.6.2

That worked! Many Thanks. The quotes must have been messing up CMake somehow. This issue is now resolved. Luke From: David Cole [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 12:34 PM To: Luke Kucalaba Cc: cmake@cmake.org Subject: Re:

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

I wrote a simple example project that is structured similarly to our real project, and it worked fine. I am going to keep working on this example project to get closer and closer to the real project until we isolate exactly what the problem is. Thanks for the suggestion. Luke -Original

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

The attachment was shot down. I renamed to .png and reattached. So you will have to rename from .png to .zip when you download it. Maybe this will work? Any suggestions on how to post this project? Luke -Original Message- From: Luke Kucalaba Sent: Thursday, October 09, 2008 1:19 PM

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Luke Kucalaba wrote: the strategy we have used to set the compiler definitions for each build configuration CMake 2.6 provides an explicit feature for this: http://www.cmake.org/Wiki/CMake_2.6_Notes#Preprocessor_Definitions

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Luke Kucalaba wrote: The attachment was shot down. I renamed to .png and reattached. So you will have to rename from .png to .zip when you download it. Maybe this will work? Any suggestions on how to post this project? I should have looked at your example closer I think the problem

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Good catch. That seems to have fixed the example--I'll try to apply the same fix to the real project to see if this is going to be resolved now. Thanks for looking into this for me, I really appreciate your time and effort. The only reason that I wanted to use the cache is to hide certain cmake

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Thanks for the links. I had never seen that CMake_2.6_Notes page before... I don't see it linked from the CMake Wiki home or CMake main website. It sounds like the whole concept of build configurations has been upgraded with 2.6. In my situation, I would want to use the set target properties

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Luke Kucalaba wrote: First problem is that you will still have build configurations in your MSVC project regardless. There is no way that I know of to disable generation of build configurations in MSVC. This is just the way the VS IDE works. A basic CMake design principle is to follow the

Re: [CMake] MSVC71 problems when upgrading to CMake 2.6.2

Thanks Brad. Sorry if I come across as upset or cynical, but I'm really just frustrated... it's been a long week. But with your help and Bill's help I think we are finally ready to move to CMake 2.6.2! CMake really is the greatest build system I've ever used, and has a lot of potential as well.