Hi David,
http://public.kitware.com/Bug/view.php?id=11896
Thanks,
Shash
-Original Message-
From: cmake-boun...@cmake.org on behalf of David Cole
Sent: Tue 3/29/2011 12:56 PM
To: cmake; CMake Developers
Subject: [CMake] Bug fix requests for the *next* release of CMake...
Hi all,
Now
,
Shash
-Original Message-
From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
Sent: Sun 3/27/2011 11:24 AM
To: cmake@cmake.org
Cc: Chatterjee, Shash
Subject: Re: [CMake] Eclipse generator - scanner-discovered include pathsand
pre-processor symbols
Ah, indeed, it was using
Hi Alex,
- CMakeFindEclipseCDT4.cmake : this is slightly changed version from the one
shipped with cmake 2.8.4, it produces debug output. Please replace the
CMakeFindEclipseCDT4.cmake in your cmake 2.8.4 installation with this file.
Then create a fresh and empty build directory, and let cmake
BTW, the command I used for cmake was:
cd build/eclipsetest
cmake -GEclipse CDT4 - Unix Makefiles
-DECLIPSE_CDT4_GENERATE_SOURCE_PROJECT=TRUE -DCMAKE_BUILD_TYPE=Debug
../../eclipsetest
-Original Message-
From: Chatterjee, Shash
Sent: Thu 3/24/2011 8:47 AM
To: a.neundorf-w...@gmx.net
I am using 2.8.4 (on Fedora Core 13).
-Original Message-
From: Alexander Neundorf [mailto:a.neundorf-w...@gmx.net]
Sent: Wed 3/16/2011 12:04 PM
To: Chatterjee, Shash
Cc: cmake@cmake.org
Subject: Re: [CMake] Eclipse generator - scanner-discovered include pathsand
pre-processor symbols
Hi Alex,
Yes, that is correct, that one pathentry line added to .cproject is all that is
needed from the generator. The scanner simply detects the built-in symbols and
paths and sticks them in the container. Then, the container contribution has
to be added as part of the project paths.
Hi Alex,
The included dirs and preprocessor symbols that are added, come from the CMake
definitions, and are needed. The container defintion is different, it adds the
dirs and symbols that are built-in to the compiler/pre-processor, and the
scanner detects those within Eclipse/CDT. So, yes
Hi,
Using CDT-2.8.2 on Fedora Core 14, and Eclipse Indigo/CDT (20101216-1529).
Most everything works fine in the .project/.cproject, except the CDT indexer
cannot find the compiler's built-in include paths/files and pre-processor
symbols. To fix that, all that has to be done is to go into the
[mailto:david.c...@kitware.com]
Sent: Thursday, February 17, 2011 3:40 PM
To: Chatterjee, Shash
Subject: Re: [CMake] Including an external object file (.o) into static shared
library using MS Visual Studio generator
Create a bug report if you can attach an example project that
demonstrates the issue
Hi!
I need to include a 3rd-party API, which comes without source, as an
object (.o) file into a static library using CMake 2.8.3. I know it is
possible to add the .o when executables are linked, but that is not the
preferred method.
I have simply defined the .o file in the ADD_LIBRARY
the ClInstall element for the .o
file, and it does not get included in the library.
Thanks,
Shash
-Original Message-
From: David Cole [mailto:david.c...@kitware.com]
Sent: Thursday, February 17, 2011 12:23 PM
To: Chatterjee, Shash
Cc: cmake@cmake.org
Subject: Re: [CMake] Including
11 matches
Mail list logo
