Sorry, I misread your message. The following works for me:
<8--
cmake_minimum_required(VERSION 2.8)
project(static)
set(CMAKE_STATIC_LIBRARY_PREFIX)
add_library(a STATIC a.c)
add_library(b STATIC b.c)
>8--
Michael
On 11/07/2011 05:14 PM, Schuchard, Matthew wrot
On 11/02/2011 04:19 PM, Jaonary Rabarisoa wrote:
> Hi all,
>
> I'm using the command install(EXPORT ) to create a configuration file for
> my project. This works great but by default
> cmake fills the IMPORTED_LINK_INTERFACE_LIBRARIES and
> IMPORTED_LINK_DEPENDENTS_LIBRARIES. I'd like cmake
> to i
On 11/04/2011 06:19 AM, Michael Wild wrote:
> On 11/03/2011 07:23 PM, Bill Hoffman wrote:
>> On 11/3/2011 1:19 PM, Paul Whelan wrote:
>>> Hi guys,
>>>
>>> I have a possibly naive question about cmake. I've got three
>>> applications that build with cmake. Normally they build and run
>>> independent
On 11/04/2011 06:39 PM, Paul Hansen wrote:
> Hi
>
> I have several small projects. Some of them may include another project.
> I have one big project that includes all small projects.
> File structure:
> projects
> - p1.cmake (add_subdirectory(dir_project1))
> - p2.cmake (add_subdirectory(dir_proj
On 11/07/2011 03:26 PM, Hendrik Sattler wrote:
> Am 07.11.2011 14:49, schrieb Daniel Dekkers:
>> Hi Hendrik,
>>
>> Could you write a few more lines. I want to understand,... but I
>> don't. ;-)
>>
>> We only have one copy of Bullet "as a bundle" present on the system.
>> Let's
>> say you just dow
On 11/07/2011 05:14 PM, Schuchard, Matthew wrote:
> Thanks for the response.
>
> Actually, that is what I want to do:
>
> "> Specifically, I need to remove the prefix "lib" from all statically
>> linked libraries I build."
>
> Also, I do not have to specify full paths to libraries I link to beca
On 11/07/2011 05:55 PM, Tomasz Grobelny wrote:
> Thanks. But it still means that I have to construct the .lib file name
> sort of manually. And possibly put some IF(WIN32)'s in my CMakeLists.txt. I
> would much prefer to have a list of all files that were produced by given
> target.
Getting such a
On 11/07/2011 05:51 PM, Tomasz Grobelny wrote:
> I have a project which is configured in several CMakeLists.txt files. The
> problem is that add_custom_command works or doesn't work depending on where
> the command is located. If I put add_custom_command just after add_library
> then it works fine.
On 11/06/2011 09:27 AM, Michael Wild wrote:
> On 11/05/2011 09:59 PM, Michael Hertling wrote:
>> On 11/02/2011 05:36 PM, Michael Wild wrote:
>>> Thanks ;-)
>>>
>>> Michael
>>
>> Just an additional remark: Instead of generating the proxy headers
>> in CMakeLists.txt, i.e. at configuration time, one
I think the main use case for saying non-additive would be useful is:
Having several targets in a given directory, most of which simply use
the directory's property value, which contains several include
directories. Now... have one target where you want to restrict the
include_directories to a sin
How would it not be additive?
get_target_property() for INCLUDE_DIRECTORIES would return target includes
+ directory includes (that apply to that target, transitively)
I don't know if preprocessor definitions follow this but this is the
behavior I would expect.
-
Robert Dailey
On Mon,
On Friday 04 November 2011, David Cole wrote:
> On Wed, Nov 2, 2011 at 8:30 PM, Stephen Kelly wrote:
> > David Cole wrote:
> >> On Tue, Nov 1, 2011 at 4:33 PM, Robert Dailey
> >>
> >> wrote:
> >>> On Tue, Nov 1, 2011 at 3:32 PM, David Cole
> >>>
> >>> wrote:
> Not yet
> >>>
> >>> Meaning
Thanks. But it still means that I have to construct the .lib file name
sort of manually. And possibly put some IF(WIN32)'s in my CMakeLists.txt. I
would much prefer to have a list of all files that were produced by given
target.
--
Regards,
Tomasz Grobelny
On Mon, 07 Nov 2011 08:27:08 -0500 (EST)
I have a project which is configured in several CMakeLists.txt files. The
problem is that add_custom_command works or doesn't work depending on where
the command is located. If I put add_custom_command just after add_library
then it works fine. Like this:
add_library(mylib SHARED ${SOURCES} ${PRI
Thanks for the response.
Actually, that is what I want to do:
"> Specifically, I need to remove the prefix "lib" from all statically
> linked libraries I build."
Also, I do not have to specify full paths to libraries I link to because of the
CMAKE_STATIC_LIBRARY_PREFIX command I had mentioned i
On 11/07/2011 04:15 PM, Schuchard, Matthew wrote:
> I am trying to globally set target properties for an entire configuration.
>
> Specifically, I need to remove the prefix βlibβ from all statically
> linked libraries I build.
>
>
>
> I already used CMAKE_STATIC_LIBRARY_PREFIX ββ such that all
I am trying to globally set target properties for an entire configuration.
Specifically, I need to remove the prefix "lib" from all statically linked
libraries I build.
I already used CMAKE_STATIC_LIBRARY_PREFIX "" such that all libraries I
explicitly link to will not have CMake search for libra
Am 07.11.2011 14:49, schrieb Daniel Dekkers:
Hi Hendrik,
Could you write a few more lines. I want to understand,... but I
don't. ;-)
We only have one copy of Bullet "as a bundle" present on the system.
Let's
say you just downloaded Bullet.
With BULLET_ROOT, we set the root path to that copy
Hi Hendrik,
Could you write a few more lines. I want to understand,... but I don't. ;-)
We only have one copy of Bullet "as a bundle" present on the system. Let's
say you just downloaded Bullet.
With BULLET_ROOT, we set the root path to that copy and do a
find_package(BULLET), it returns with:
I think the CMAKE_SHARED_LIBRARY_PREFIX/CMAKE_SHARED_LIBRARY_SUFFIX variables
would tell you what you want. We use them to determine the output name as:
${CMAKE_SHARED_LIBRARY_PREFX}${CMAKE_SHARED_LIBRARY_SUFFIX}
We also have an if statement in case STATIC libraries are built, in which case
you
I have a library created like this:
add_library(mylib SHARED ${SOURCES} ${PRIVATE_HEADERS}
${PUBLIC_HEADERS})
Now I want to get names of all output files for mylib target (on Unix this
would be .so file, but on Windows it would be .dll, .lib and possibly .pdb
files). Is there any better way to ge
Am 07.11.2011 12:04, schrieb Daniel Dekkers:
Just a thought.
Just a thought on your thought.
We are incorporating 3rd party library Bullet in our own library.
This can
be done on two levels (via an option). Either by sources (which is
standard
practice with Bullet), or by linking to the buil
Hi,
Just a thought.
We are incorporating 3rd party library Bullet in our own library. This can
be done on two levels (via an option). Either by sources (which is standard
practice with Bullet), or by linking to the built Bullet libraries directly.
Now find_package(BULLET) (i.e. the findBull
Hello,
this weekend I had trouble downloading CMake. Not sure if it
the problem was on my side or if it was at www.cmake.org, but
each time I tried to download the setup for 2.8.6 (or indeed
the source code) I ended up on the page "public.kitware.com".
The problem has gone now and I have downloa
24 matches
Mail list logo