Le 31/08/2018 à 16:31, Eric Noulard a écrit :
Le ven. 31 août 2018 à 15:59, Stéphane Ancelot
mailto:sance...@numalliance.com>> a écrit :
I ended with :
add_custom_target(combined ALL
COMMAND ${CMAKE_AR} rc libcombined.a $
$)
Quick & dirty :-)
There is the "thin" optio
Le ven. 31 août 2018 à 15:59, Stéphane Ancelot a
écrit :
> I ended with :
>
> add_custom_target(combined ALL
>COMMAND ${CMAKE_AR} rc libcombined.a $ $ FILE:lib2>)
>
Quick & dirty :-)
There is the "thin" option of ar as well:
https://stackoverflow.com/questions/3821916/how-to-merge-two-ar-sta
I ended with :
add_custom_target(combined ALL
COMMAND ${CMAKE_AR} rc libcombined.a $
$)
Le 31/08/2018 à 15:24, Eric Noulard a écrit :
First create OBJECT libraries instead of static
Then create as many STATIC libraries as you want that includes as many
OBJECT libraries content as you wan
First create OBJECT libraries instead of static
Then create as many STATIC libraries as you want that includes as many
OBJECT libraries content as you want.
Le ven. 31 août 2018 à 15:17, Stéphane Ancelot a
écrit :
> Hi,
>
> I have got some static libraries generated, that I would like to put i
Hi,
I have got some static libraries generated, that I would like to put in
a common one.
how can I proceed ?
Regards,
S.Ancelot
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services t
Thanks to all who have replied for your efforts in trying to help me. My
apologies for any lack of clarity in describing my problem.
With the various information and advice you provided, I have been able to
get my CMake configuration working.
Thanks again!
..chris
On Wed, Nov 26, 2014 at 3:30
Chris Johnson wrote:
> * I do not want to use the add_library(component1 OBJECT
> ${component1_sources}) and add_library(toplevel
> $ ... ) syntax if it can be avoided.
Is the constraint that you want a top-level something like
# All components:
set(components component1 component2)
fore
nson [cxjohn...@gmail.com]
> Sent: Wednesday, November 26, 2014 8:45 PM
> To: Mueller-Roemer, Johannes Sebastian
> Cc: cmake@cmake.org
> Subject: Re: [CMake] Creating a library from subdirectories
>
> I know that one cannot link static libraries together; they're just
archives o
that CMake knows that those have to be linked
as well.
From: Chris Johnson [cxjohn...@gmail.com]
Sent: Wednesday, November 26, 2014 8:45 PM
To: Mueller-Roemer, Johannes Sebastian
Cc: cmake@cmake.org
Subject: Re: [CMake] Creating a library from subdirectories
I
ax +49 6151 155-139
>
> johannes.mueller-roe...@igd.fraunhofer.de | www.igd.fraunhofer.de
>
>
>
> *From:* Mueller-Roemer, Johannes Sebastian
> *Sent:* Wednesday, November 26, 2014 13:50
> *To:* 'Chris Johnson'; cmake@cmake.org
> *Subject:* RE: [CMake] Creating a libr
-Roemer, Johannes Sebastian
Sent: Wednesday, November 26, 2014 13:50
To: 'Chris Johnson'; cmake@cmake.org
Subject: RE: [CMake] Creating a library from subdirectories
In the example on that site an OBJECT library is created (the output consists
of multiple .obj files), you used STATIC librari
, 2014 01:36
To: cmake@cmake.org
Subject: [CMake] Creating a library from subdirectories
This CMake wiki page (http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library)
claims one can create a library from subdirectories containing libraries, which
is exactly what I want to do. However, it doesn&#
This CMake wiki page (
http://www.cmake.org/Wiki/CMake/Tutorials/Object_Library) claims one can
create a library from subdirectories containing libraries, which is exactly
what I want to do. However, it doesn't seem to work. Here's my SSCCE (
http://sscce.org) "toy" example file structure:
.
|--
thanks Eric!
Cristobal
On Tue, Sep 13, 2011 at 7:12 PM, Eric Noulard wrote:
> 2011/9/13 Cristobal Navarro :
> > hello everyone!
> > this is my first post on the mailing list
> > i am making a shared library
> > i have everything configured properly so that cmake creates de makefile
> > scripts a
2011/9/13 Cristobal Navarro :
> hello everyone!
> this is my first post on the mailing list
> i am making a shared library
> i have everything configured properly so that cmake creates de makefile
> scripts as espected
> at the moment cmake is installing my library by default into:
> /usr/local/lib
hello everyone!
this is my first post on the mailing list
i am making a shared library
i have everything configured properly so that cmake creates de makefile
scripts as espected
at the moment cmake is installing my library by default into:
/usr/local/lib/mylib.so.0.1 (and the symlink mylib.so)
Ah of course! I am just used to doing
ADD_EXECUTABLE(Test1 Test1.cpp ${Sources})
So I guess I wasn't thinking and assumed it would be the same for
libraries, but now MyLibs is an actual "thing", not a list of files
like ${Sources} is.
Thanks guys.
David
On Wed, Feb 18, 2009 at 12:46 PM, Bill
David Doria wrote:
If I have many executables in the same project (ie same CMakeLists.txt
file), it seems like I shouldn't have to do this:
set(Sources File1.cpp File1.cpp )
ADD_EXECUTABLE(Test1 Test1.cpp ${Sources})
ADD_EXECUTABLE(Test2 Test2.cpp ${Sources})
because it is compiling File1 and
Off the top of my head I think
TARGET_LINK_LIBRARIES(Test1 ${MyLibs})
should be
TARGET_LINK_LIBRARIES(Test1 MyLibs)
Also, I think you need to specify a static library if you want one. It seems
like a static library is what you want in this case.
I wrote this up really quick, and could be wrong ab
If I have many executables in the same project (ie same CMakeLists.txt
file), it seems like I shouldn't have to do this:
set(Sources File1.cpp File1.cpp )
ADD_EXECUTABLE(Test1 Test1.cpp ${Sources})
ADD_EXECUTABLE(Test2 Test2.cpp ${Sources})
because it is compiling File1 and File2 twice when tha
20 matches
Mail list logo
