Re: [CMake] disable compiler test

In a distributed environment of C++ projects, with multiple external dependencies, it is generally a good practice to stick with one compiler version until all of the dependencies can be updated to the newer compiler version. I'm in the process of notifying the guy who cares about these types of t

Re: [CMake] Project being (unnecessarily) relinked

Jesper Eskilson wrote: Matthew Smith wrote: Jesper Eskilson wrote: I'm still very much interested in an answer to this question. Regarding suppressing unnecessary relinking, I had a similar problem in my application (QTM) in which it was relinked at "make install" stage, often to a differ

Re: [CMake] Project being (unnecessarily) relinked

Matthew Smith wrote: Jesper Eskilson wrote: I'm still very much interested in an answer to this question. Regarding suppressing unnecessary relinking, I had a similar problem in my application (QTM) in which it was relinked at "make install" stage, often to a different version of Qt to the

Re: [CMake] disable compiler test

Juan Sanchez wrote: Hi Bill, Currently we are using gcc 3.4.0 and 4.1.1. Our systems are ancient and are using Redhat Enterprise 3 or 4. The version of ld is too old, and it is being passed a flag by gcc 4.1.1 it doesn't recognize. Curiously g++ 4.1.1 doesn't have this problem. Neither does

Re: [CMake] disable compiler test

Hi Bill, Currently we are using gcc 3.4.0 and 4.1.1. Our systems are ancient and are using Redhat Enterprise 3 or 4. The version of ld is too old, and it is being passed a flag by gcc 4.1.1 it doesn't recognize. Curiously g++ 4.1.1 doesn't have this problem. Neither does gcc 4.2.0. The only "

Re: [CMake] disable compiler test

Juan Sanchez wrote: How do you disable the compiler test? Our version of gcc is passing a bad compiler option (--as-needed) to ld and it is causing cmake to fail. This is ok since g++ still seems to work properly. Disabling the test is a bad idea, as cmake will use the same code to create y

Re: [CMake] disable compiler test

Juan Sanchez wrote: How do you disable the compiler test? Our version of gcc is passing a bad compiler option (--as-needed) to ld and it is causing cmake to fail. This is ok since g++ still seems to work properly. Disable C in the project: PROJECT(FOO CXX) The default PROJECT(FOO) Will te

[CMake] disable compiler test

How do you disable the compiler test? Our version of gcc is passing a bad compiler option (--as-needed) to ld and it is causing cmake to fail. This is ok since g++ still seems to work properly. Thanks, Juan ___ CMake mailing list CMake@cmake.org ht

Re: [CMake] Project being (unnecessarily) relinked

Jesper Eskilson wrote: I'm still very much interested in an answer to this question. Regarding suppressing unnecessary relinking, I had a similar problem in my application (QTM) in which it was relinked at "make install" stage, often to a different version of Qt to the one I had chosen to l

RE: [CMake] Visual SourceSafe and Relative Paths for MSVC

That doesn't work for me for some reason. I am using the latest release. -Tal -Original Message- From: Sylvain Benner [mailto:[EMAIL PROTECTED] Sent: Monday, September 10, 2007 6:05 AM To: Tal Blum Cc: cmake@cmake.org Subject: Re: [CMake] Visual SourceSafe and Relative Paths for MSVC

Re: [CMake] basename macro

2007/9/10, Juan Sanchez <[EMAIL PROTECTED]>: > Is there a basename macro to remove the file extension from a name? I > am using 2.4.7. Look at the GET_FILENAME_COMPONENT CMake builtin macro. >>> Get a specific component of a full filename. GET_FILENAME_COMPONENT(VarName FileName

Re: [CMake] basename macro

On Sep 10, 2007, at 10:19 AM, Juan Sanchez wrote: Is there a basename macro to remove the file extension from a name? I am using 2.4.7. Thanks, Juan What you want is GET_FILENAME_COMPONENT. From cmake --help-full | less GET_FILENAME_COMPONENT Get a specific component of a full fi

[CMake] basename macro

Is there a basename macro to remove the file extension from a name? I am using 2.4.7. Thanks, Juan ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake

[CMake] Framework

I want to use a framework for the includes and library linkage. FIND_LIBRARY seems like it will work for the library, but what about the include. Should I use a FIND_FILE followed by a INCLUDE_DIRECTORIES. I want to link against the Apple profiling library found in /System/ Library/Priva

Re: [CMake] Project being (unnecessarily) relinked

Jesper Eskilson wrote: > Mathieu Malaterre wrote: >> On 9/4/07, Jesper Eskilson <[EMAIL PROTECTED]> wrote: >>> Hi! >>> >>> I've got a Visual Studio 8 solution generated by CMake where one of the >>> projects is always being relinked everytime I build it, even when >>> nothing in it has changed (i.e

Re: [CMake] Visual SourceSafe and Relative Paths for MSVC

It seems that although when I add a file to a library with a relative path, the resulting MSVC project contains the file with an absolute path. While it works for compiling, it doesn’t work for the Microsoft visual source safe plug-in in Visual Studio. Does Cmake support Microsoft’s visual so

Re: [CMake] Output name and path depeding on debug/release mode

On 9/6/07, Fieselmann, Andreas (ext) <[EMAIL PROTECTED]> wrote: > > > Dear CMake users! > > I am using Visual C++ 6.0 and I'd like to have different output names for > the dlls I am building depending if they are in release or debug mode. > Additionally they should be placed in a certain path. > Fo