Hi,
I somewhat recently filed a bug report regarding target_link_libraries
favoring target names over library names
(https://gitlab.kitware.com/cmake/cmake/issues/17911). Brad King
suggested also that I switch to UNKNOWN instead of INTERFACE for the
IMPORTed targets created by my find-modules.
In
01.09.2016, 08:34, "n...@appletonaudio.com" :
> On 2016-08-31 23:32, Konstantin Tokarev wrote:
>> 31.08.2016, 16:22, "Nick Appleton" :
>>> Hi,
>>>
>>> I’ve been recently doing a bit of work for an open source project
>>> trying to extend it’s support for CMake. I’ve been trying to get CMake
>
On 2016-08-31 23:32, Konstantin Tokarev wrote:
31.08.2016, 16:22, "Nick Appleton" :
Hi,
I’ve been recently doing a bit of work for an open source project
trying to extend it’s support for CMake. I’ve been trying to get CMake
to be able to replicate most of the functionality which can be
achi
31.08.2016, 16:22, "Nick Appleton" :
> Hi,
>
> I’ve been recently doing a bit of work for an open source project trying to
> extend it’s support for CMake. I’ve been trying to get CMake to be able to
> replicate most of the functionality which can be achieved with the existing
> autoconf-based
Hi,
I’ve been recently doing a bit of work for an open source project trying to
extend it’s support for CMake. I’ve been trying to get CMake to be able to
replicate most of the functionality which can be achieved with the existing
autoconf-based infrastructure (and have had pretty good success)
Hello there.
First of all is there any documentation about how CMake handles
deduplication of libraries when linking (so to avoid duplicate libraries to
be linked unnecessarily)?
Now to my issue: I have a library libA which has to link to libB, libC,
libD and libE.
libA is the only one internal to
ExternalProject makes no assumptions about what is being built. It
could just be a collection of executables, or maybe nothing is built
at all. It is up to the project being built to provide facilities for
accessing its targets in a platform-independent way. For example, the
external project can in
Hello,
I use the ExternalProject_Add command to download and build a static library
called 'foo.a'.
I build another library 'bar' which depends on 'foo.a'.
For the moment, I use the target_link_libraries command to create a link
between foo and bar:
target_link_libraries(bar ${FOO_INSTALL
We use similar layout in a set of components, but in order to do that we just
store library interface headers in /include/ directory. And
layout of library directory is the following:
src/ - internal headers and implementation
include/ - external headers
CMakeLists.txt
Then you can define the f
, January 19, 2015 5:14 PM
To: cmake@cmake.org
Subject: [CMake] Library include path question
A common and useful method for avoiding name conflicts and keeping files
well-organized is to place them in a subdirectory unique to the library. For
example, the libraries for Graphviz and Postgres often
A common and useful method for avoiding name conflicts and keeping files
well-organized is to place them in a subdirectory unique to the library.
For example, the libraries for Graphviz and Postgres often install their
API header files in directories named /include/graphviz and
/include/libpq. So
On Mon, Nov 17, 2014 at 10:26 PM, Stephen Kelly wrote:
> avo...@mail.ru wrote:
>
>> What should I add
>> to B/CMakeLists.txt to successfully build my executable?
>
> You might be able to add an INTERFACE library and populate its
> INTERFACE_SOURCES using the target_sources command:
>
> http://www
avo...@mail.ru wrote:
> What should I add
> to B/CMakeLists.txt to successfully build my executable?
You might be able to add an INTERFACE library and populate its
INTERFACE_SOURCES using the target_sources command:
http://www.cmake.org/cmake/help/v3.1/command/target_sources.html
http://ww
Hello!
I'm playing with add_library(OBJECT) operation. Everything works nice
but then I have one "library" that uses some external library. An
attempt to add target_link_libraries here results in failure, because I
don't build and library, only object files. But now comes the problem,
how do I not
Hello,
I have cmake project, which tries to link against external libraries using
target_link_libraries(myExec ${EXTERNAL_LIBS})
When compiling and linking the executable using make, I can see that
some libraries are doubled in the link line, but not all.
At the current stage, I think, that th
On 6 December 2012 18:45, Andreas Pakulat wrote:
> On Thu, Dec 6, 2012 at 5:13 PM, Mateusz Loskot wrote:
>> The CMake 2.8.10 manual includes the following statement in the paragraph
>> about link_directories() command:
>>
>> "Library locations returned by find_package() and find_library() are
>>
Hi,
On Thu, Dec 6, 2012 at 5:13 PM, Mateusz Loskot wrote:
> The CMake 2.8.10 manual includes the following statement in the paragraph
> about link_directories() command:
>
> "Library locations returned by find_package() and find_library() are
> absolute paths."
>
> Would it be possible to include
Hi,
The CMake 2.8.10 manual includes the following statement in the paragraph
about link_directories() command:
"Library locations returned by find_package() and find_library() are
absolute paths."
Would it be possible to include similar clarification in the sections for
find_package() and find_
On Fri, Jun 17, 2011 at 4:30 PM, Eric Sokolowsky wrote:
> You didn't specify your development environment so I'm just guessing here.
> Under Linux, you usually have to install a development package in order to
> link to libraries. If you are compiling your own libgeotiff you might want
> to instal
You didn't specify your development environment so I'm just guessing here.
Under Linux, you usually have to install a development package in order to
link to libraries. If you are compiling your own libgeotiff you might want
to install the library before trying to link to it. You might also be
link
On 06/16/2011 11:56 PM, David Doria wrote:
> I added a simple:
>
> target_link_libraries(myprogram geotiff)
>
> to my CMakeLists.txt file. I have a libgeotiff.so in a directory on my
> LD_LIBRARY_PATH. The code compiled, but when I tried to run it, I got
> an error that I was missing libgeotiff.s
I added a simple:
target_link_libraries(myprogram geotiff)
to my CMakeLists.txt file. I have a libgeotiff.so in a directory on my
LD_LIBRARY_PATH. The code compiled, but when I tried to run it, I got
an error that I was missing libgeotiff.so.2. I made a symlink from
libgeotiff.so.2 to libgeotiff.
Am 11.06.2011 16:21, schrieb Michael Hertling:
On 06/10/2011 12:57 PM, Andreas Naumann wrote:
Am 10.06.2011 00:16, schrieb Michael Hertling:
On 06/09/2011 08:18 AM, Andreas Naumann wrote:
Am 09.06.2011 07:35, schrieb Michael Hertling:
On 06/09/2011 07:13 AM, Andr
On 06/10/2011 12:57 PM, Andreas Naumann wrote:
> Am 10.06.2011 00:16, schrieb Michael Hertling:
>> On 06/09/2011 08:18 AM, Andreas Naumann wrote:
>>
>>> Am 09.06.2011 07:35, schrieb Michael Hertling:
>>>
On 06/09/2011 07:13 AM, Andreas Naumann wrote:
> Am 08.06.
Am 10.06.2011 00:16, schrieb Michael Hertling:
On 06/09/2011 08:18 AM, Andreas Naumann wrote:
Am 09.06.2011 07:35, schrieb Michael Hertling:
On 06/09/2011 07:13 AM, Andreas Naumann wrote:
Am 08.06.2011 20:43, schrieb Andreas Pakulat:
On 08.06.11 20:00:54, Andreas
On 06/09/2011 08:18 AM, Andreas Naumann wrote:
> Am 09.06.2011 07:35, schrieb Michael Hertling:
>> On 06/09/2011 07:13 AM, Andreas Naumann wrote:
>>
>>> Am 08.06.2011 20:43, schrieb Andreas Pakulat:
>>>
On 08.06.11 20:00:54, Andreas Naumann wrote:
> Am 08.06.201
2011/6/8 Andreas Naumann :
> Am 08.06.2011 15:02, schrieb Eric Noulard:
>>
>> 2011/6/8 Andreas Naumann:
>>
>>>
>>> Am 08.06.2011 11:56, schrieb Eric Noulard:
>>>
2011/6/8 Andreas Naumann:
>
> Hi @all,
>
> I have some problem with the library usage in cmake.
>
Am 09.06.2011 07:35, schrieb Michael Hertling:
On 06/09/2011 07:13 AM, Andreas Naumann wrote:
Am 08.06.2011 20:43, schrieb Andreas Pakulat:
On 08.06.11 20:00:54, Andreas Naumann wrote:
Am 08.06.2011 15:02, schrieb Eric Noulard:
2011/6/8 Andreas Naumann:
On 06/09/2011 07:13 AM, Andreas Naumann wrote:
> Am 08.06.2011 20:43, schrieb Andreas Pakulat:
>> On 08.06.11 20:00:54, Andreas Naumann wrote:
>>
>>> Am 08.06.2011 15:02, schrieb Eric Noulard:
>>>
2011/6/8 Andreas Naumann:
> Am 08.06.2011 11:56, schrieb Eric Noulard:
Am 08.06.2011 20:43, schrieb Andreas Pakulat:
On 08.06.11 20:00:54, Andreas Naumann wrote:
Am 08.06.2011 15:02, schrieb Eric Noulard:
2011/6/8 Andreas Naumann:
Am 08.06.2011 11:56, schrieb Eric Noulard:
2011/6/8 Andreas Naumann:
Hi @all,
I have some
On 08.06.11 20:00:54, Andreas Naumann wrote:
> Am 08.06.2011 15:02, schrieb Eric Noulard:
> >2011/6/8 Andreas Naumann:
> >>Am 08.06.2011 11:56, schrieb Eric Noulard:
> >>>2011/6/8 Andreas Naumann:
> >>>
> Hi @all,
>
> I have some problem with the library usage in cmake.
>
> It
Am 08.06.2011 15:02, schrieb Eric Noulard:
2011/6/8 Andreas Naumann:
Am 08.06.2011 11:56, schrieb Eric Noulard:
2011/6/8 Andreas Naumann:
Hi @all,
I have some problem with the library usage in cmake.
It seems to me, that cmake removes the full path of the library, if the
p
2011/6/8 Andreas Naumann :
> Am 08.06.2011 11:56, schrieb Eric Noulard:
>>
>> 2011/6/8 Andreas Naumann:
>>
>>>
>>> Hi @all,
>>>
>>> I have some problem with the library usage in cmake.
>>>
>>> It seems to me, that cmake removes the full path of the library, if the
>>> path
>>> is in the environment
Am 08.06.2011 11:56, schrieb Eric Noulard:
2011/6/8 Andreas Naumann:
Hi @all,
I have some problem with the library usage in cmake.
It seems to me, that cmake removes the full path of the library, if the path
is in the environment variable LIBRARY_PATH.
This behaviour cause problems at our
2011/6/8 Andreas Naumann :
> Hi @all,
>
> I have some problem with the library usage in cmake.
>
> It seems to me, that cmake removes the full path of the library, if the path
> is in the environment variable LIBRARY_PATH.
> This behaviour cause problems at our system, such that the linker links
>
Hi @all,
I have some problem with the library usage in cmake.
It seems to me, that cmake removes the full path of the library, if the
path is in the environment variable LIBRARY_PATH.
This behaviour cause problems at our system, such that the linker links
against the wrong library.
Is there
On 24. Aug, 2010, at 10:21 , Diablo 666 wrote:
>
> Hi,
>
> is there a way to use the CMAKE_*_POSTFIX variables for libraries which are
> not targets of the current project? I'd like to avoid the "optimized Foo
> debug FooD" construct. (Actually, linking against other targets of the
> current
Hi,
is there a way to use the CMAKE_*_POSTFIX variables for libraries which are not
targets of the current project? I'd like to avoid the "optimized Foo debug
FooD" construct. (Actually, linking against other targets of the current
project works well with only "Foo")
Best regards.
Andreas
On Thursday 29 July 2010, Eric Noulard wrote:
> 2010/7/29 Clifford Yapp :
> > Got it - was using a VTK macro for third_party inclusion that was
> > using SUBDIRS - switching it to ADD_DIRECTORY got me going. Awesome!
>
> SUBDIRS is deprecated but it's good to know that it's behavior
> is not stric
2010/7/29 Clifford Yapp :
> Got it - was using a VTK macro for third_party inclusion that was
> using SUBDIRS - switching it to ADD_DIRECTORY got me going. Awesome!
SUBDIRS is deprecated but it's good to know that it's behavior
is not strictly equivalent to ADD_DIRECTORY in some case.
--
Erk
M
Got it - was using a VTK macro for third_party inclusion that was
using SUBDIRS - switching it to ADD_DIRECTORY got me going. Awesome!
Thanks!
CY
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/openso
2010/7/28 Clifford Yapp :
> Ironically, I now see this issue (almost exactly) was discussed long ago:
>
> http://www.cmake.org/pipermail/cmake/2005-September/007204.html
>
> However, when I try:
>
> get_directory_property(PNG_LIB_NAME DIRECTORY src/other/libpng
> DEFINITION PNG_LIB_NAME)
> MESSAGE(
Ironically, I now see this issue (almost exactly) was discussed long ago:
http://www.cmake.org/pipermail/cmake/2005-September/007204.html
However, when I try:
get_directory_property(PNG_LIB_NAME DIRECTORY src/other/libpng
DEFINITION PNG_LIB_NAME)
MESSAGE("getdirprop: ${PNG_LIB_NAME}")
I get not
OK, I've had more time to play with CMake and subdirectory
CMakeList.txt files, and I'm getting close to the behavior I want. I
can conditionally override key variables to use either local or system
versions of a library, and I can trigger the builds conditionally as
well. Using the strings defin
>linking your executable to those libs or are you doing
>something like "dlopen" inside your application?
>
>--
>Erk
>Membre de l'April - « promouvoir et défendre le logiciel libre » -
>http://www.april.org
Thanks for the response. The executable uses dlopen at runtime and was
pointing to the "s
2010/7/19 :
> When I do an in-source build, everything runs ok. However, I have
> issues with an out-of-source build. One of my libraries uses another
> one of my libraries. When I run the executable it complains "cannot
> open shared object file: No such file or directory."
linking your execu
When I do an in-source build, everything runs ok. However, I have
issues with an out-of-source build. One of my libraries uses another
one of my libraries. When I run the executable it complains "cannot
open shared object file: No such file or directory." It's looking for
the library in the sou
On 05/27/2010 05:32 PM, Torri, Stephen CIV NSWCDD, W15 wrote:
>> From: cmake-boun...@cmake.org on behalf of Doug Reiland
>> Sent: Thu 5/27/2010 11:14 AM
>> To: cmake@cmake.org
>> Subject: [CMake] cmake - library help
>>
>> First, I am new to cmake and explo
-boun...@cmake.org] On Behalf
Of Torri, Stephen CIV NSWCDD, W15
Sent: Thursday, May 27, 2010 12:42 PM
To: Doug Reiland
Cc: cmake@cmake.org
Subject: Re: [CMake] cmake - library help
> From: Doug Reiland [mailto:dreil...@gmail.com]
> Sent: Thu 5/27/2010 12:48 PM
> To: Torri, Stephen CIV NSWCDD, W15
tephen CIV NSWCDD, W15
wrote:
>> From: cmake-boun...@cmake.org on behalf of Doug Reiland
>> Sent: Thu 5/27/2010 11:14 AM
>> To: cmake@cmake.org
>> Subject: [CMake] cmake - library help
>>
>> First, I am new to cmake and exploring converting our home grown build
&
> From: Doug Reiland [mailto:dreil...@gmail.com]
> Sent: Thu 5/27/2010 12:48 PM
> To: Torri, Stephen CIV NSWCDD, W15
> Subject: Re: [CMake] cmake - library help
>
> ok, I think I have this working, thanks.
> I am building static version of "foo" as well.
> Be
> From: cmake-boun...@cmake.org on behalf of Doug Reiland
> Sent: Thu 5/27/2010 11:14 AM
> To: cmake@cmake.org
> Subject: [CMake] cmake - library help
>
> First, I am new to cmake and exploring converting our home grown build system.
> How would I code this up in cmake
>
First, I am new to cmake and exploring converting our home grown build system.
How would I code this up in cmake
I have composite objects that need to be added to a share library
add_library(foo a.c b.c c.c)
I also need x.o in the library AND x.o linked from:
subdir-a/aa.c subdir-a/bb.c
Thank
LINK_INTERFACE_LIBRARIES was exactly what I needed. Thanks!
As for moving the .lib that was generated for the .dll, I've made piece with
keeping that at its default output location. CMake is smarter with linking
than I originally thought.
On Fri, Jun 26, 2009 at 12:28 AM, Tyler Roscoe wrote:
>
On Thu, Jun 25, 2009 at 09:54:11PM -0500, Nathan Paul wrote:
> When I tell MessageTest to link to Messages (using target_link_libraries and
> specifying the Messages library), the Google Protocol Buffer library is
> added as a dependency. This is undesired, since the library is already
> linked sta
Hi all,
I have a project setup with the following directory structure:
/
CMakeLists.txt
Messages/
CMakeLists.txt
MessageTest/
CMakeLists.txt
Build/
bin/
Debug/
Release/
The subdirectory "Messages" outputs a shared library called "Mess
Hello,
I'm using the different version of the OpenCV library and i would like to
make it easy to switch from one to another by changing its path in
cmake-gui.
Howerver, it seems that keeping the value in the cache make this impossible!
here a sample of my code:
IF(NOT OpenCV_FOUND)
SET (OpenCV_
On 16:24 Tue 12.05.09, Mathieu Malaterre wrote:
> See LINK_INTERFACE_LIBRARIES if you wish to achieve the behavior you
> want (I do not know what it does for static libs).
According to cmake.org "This propert is ignored for STATIC libraries.".
Now if this is the intended way to go; where can I fi
On Tue, May 12, 2009 at 3:55 PM, Simon Friedberger
wrote:
> Good Morning,
>
> after some more digging yesterday I came up with this working solution:
> http://pastebin.com/m1daf62d4
> Now if you look at lines 36-38 and 46 you will notice that I had to make
> dependencies on some libraries explicit
Good Morning,
after some more digging yesterday I came up with this working solution:
http://pastebin.com/m1daf62d4
Now if you look at lines 36-38 and 46 you will notice that I had to make
dependencies on some libraries explicit that I did not need before.
Mathieu already said this was the cmake
Hi Simon,
scan through the documentation of cmake
http://www.cmake.org/cmake/help/cmake2.6docs.html
especially the commands part:
http://www.cmake.org/cmake/help/cmake2.6docs.html#section_Commands
In order to add include directories use include_directories
http://www.cmake.org/cmake/help/
c
On Tue, May 12, 2009 at 3:33 AM, Simon Friedberger
wrote:
> Hello listmembers,
>
> I have just spent the better part of today trying to convert my old
> Makefile to a CMakeLists.txt and failed miserably. I may have made some
> major mistakes since this is my first such effort.
>
> I could not figu
Hello listmembers,
I have just spent the better part of today trying to convert my old
Makefile to a CMakeLists.txt and failed miserably. I may have made some
major mistakes since this is my first such effort.
I could not figure out how to include libraries correctly so in the end
I tried to crea
On Mon, May 11, 2009 at 05:05:33PM +0200, Michele Bosi wrote:
> Is there a way to do this thing in a portable way, something like
> "include_directories()" but for library directories?
http://www.cmake.org/cmake/help/cmake2.6docs.html#command:link_directories
tyler
___
I'm sure this question has been asked already many times but I cound't
find any info in the archive (also because it seems that the archive
is not searchable...).
I would like to know how to add a library directory flag to a target.
For now I could only find the command:
set_target_properties(WX_e
On Tue, Apr 07, 2009 at 08:30:19PM -0400, John Dey wrote:
> When I make from the root of the binary tree, I get the error below.
> Yet when I go the subdirectory clthreads, make from that dir creates
> the lib. Returning to the root and remaking eliminates the error.
>
> aeolus_build $ mak
Hi List,
I'm new to cmake and need a little help:
When I make from the root of the binary tree, I get the error below.
Yet when I go the subdirectory clthreads, make from that dir creates
the lib. Returning to the root and remaking eliminates the error.
What am I missing?
aeolus_build
OK, I finally found the problem.
It seems that I was being silly and not being consistent with case in the
project(X) call and the ${X_SOURCE_DIR} references.
Everything is working as expected now, thanks for your help guys.
On Wednesday 04 February 2009 12:19:11 Michael Jackson wrote:
> I don'
I don't think the style of include paths has anything to do with
whether or not the library will compile as a static or dynamic library.
What is the output of:
MESSAGE("SERVER_SOURCE_DIR is ${SERVER_SOURCE_DIR}")
Please post that to the list.
__
Thanks for your help.
It seems that the library cannot be compiled as static, when I tried it as
dynamic it worked without a problem. I assume that this is due to the <> style
includes as there wouldn't be a search path for a static library since it's
part of the executable.
Could anyone tell
perhaps include_directories(..)
That's how I do it.
You can also print the
${SERVER_SOURCE_DIR}
variable.
MESSAGE("SERVER_SOURCE_DIR is ${SERVER_SOURCE_DIR}")
Let me know if this works.
Nick Ogden wrote:
> Hi there,
>
> I have a problem with using CMake to compile a library that I'm trying to us
Nick Ogden wrote:
Hi there,
I see you found the right list ;-).
(And I will admit I was lazy and didn't read it before on kde-devel,
which is why I'm just now answering your actual question.)
I have a problem with using CMake to compile a library that I'm trying to use
in an application th
Hi there,
I have a problem with using CMake to compile a library that I'm trying to use
in an application that I'm writing.
I have the following directory structure:
src/
| CMakeLists.txt (1)
| app/
| | CMakeLists.txt (2)
| | (app source and headers)
|
On Fri, Sep 5, 2008 at 10:12 PM, Philip Lowman <[EMAIL PROTECTED]> wrote:
> Incidentally, CMake doesn't have "/MAP" in it's list of understood VS flags
> so it will show up under the Additional Linking Flags section of the Linker
> properties and not where you're probably used to seeing it.
>
And
On Mon, Sep 1, 2008 at 3:27 AM, Ingrid Kemgoum <[EMAIL PROTECTED]>wrote:
> hi,
> i'm trying to export only some functions of a library with cmake
> i know with windows we use *__declspec(dllimport)* and *
> __declspec(dllexport)* to generate the appropriate .lib of the dll
> is there a manner of
hi,
i'm trying to export only some functions of a library with cmake
i know with windows we use *__declspec(dllimport)* and *
__declspec(dllexport)* to generate the appropriate .lib of the dll
is there a manner of generating the .map ?
thanks a lot
___
On Wed, Feb 27, 2008 at 4:51 PM, Robert Fleming <
[EMAIL PROTECTED]> wrote:
> To solve the first problem I did:
>
> set_target_properties(rtf PROPERTIES LINK_FLAGS "/NODEFAULTLIB:msvcrt")
>
> Not sure if this is the best way. You'll want to wrap it with some
> conditional statements checking you'
To solve the first problem I did:
set_target_properties(rtf PROPERTIES LINK_FLAGS "/NODEFAULTLIB:msvcrt")
Not sure if this is the best way. You'll want to wrap it with some
conditional statements checking you're on windows, probably.
Also, if you just want to ignore a library in debug, you can
In VS you can
ignore a specific library:
Project -> Properties -> Linker -> Input -> Ignore Specific Libraries
for a lib target add your own dependencies with directory:
Project -> Properties -> Librarian -> Additional Dependencies
Project -> Properties -> Librarian -> Additional Library Director
Hi all.
I have a question regarding library dependency.
Im using VC2005.
Assume the following:
I have a solution with a set of projects, three are libraries and one is an
application:
A.lib /A.dll
B.lib/B.dll : B depends on A.lib, so if I want to use B.lib somewhere,
A.libis also automaticall
I am using a library naming convention that shows which type of run-time it
selects on windows. Specifically, a debug target would get a version name
like systemc-v2.2.0-mdd.lib, and a release target would be
systemc-v2.2.0-mdr.lib, to disambiguate multi-threaded, DLL, Debug/Release
versions.
N
On Nov 14, 2007 2:33 PM, tek <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have libfoo.so and an executable named foo, and I can't find out how to
> manage this situation. The RENAME option of INSTALL doesen't work on TARGETS,
> and if I name them both "foo", the library is installed twice. Is there a
This should work:
---
add_library(foo_lib SHARED foo_lib.c)
set_target_properties(foo_lib PROPERTIES OUTPUT_NAME foo)
add_executable(foo_exe foo_exe.c)
set_target_properties(foo_exe PROPERTIES OUTPUT_NAME foo)
---
Best regards
Gerhard
___
CMake mailin
Hello,
I have libfoo.so and an executable named foo, and I can't find out how to
manage this situation. The RENAME option of INSTALL doesen't work on TARGETS,
and if I name them both "foo", the library is installed twice. Is there a way
to accomplish this?
Greetings
signature.asc
Description
You're right, I had one reference to "libutil" accidentally!
Thanks,
Mark
On 10/29/07, Brandon Van Every <[EMAIL PROTECTED]> wrote:
> On 10/29/07, Mark Wyszomierski <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I have a library project named "lib_util".
> >
> > When using CMake to build the library
On 10/29/07, Mark Wyszomierski <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a library project named "lib_util".
>
> When using CMake to build the library (with g++), the output file is:
>
> liblib_util.a
>
> Now another sub project needs to link to that, and has the following
> in CMakeLists.txt
Hi,
I have a library project named "lib_util".
When using CMake to build the library (with g++), the output file is:
liblib_util.a
Now another sub project needs to link to that, and has the following
in CMakeLists.txt:
target_link_libraries(my_app, lib_util)
but when compiling my_app,
Hi,
I am trying to build a library with cmake using QT4 tools (moc, wrap) using
a master cmake script and lib/project related subscript. The thing is that I
have a build error then the one of the library (the one that uses QT4) tries
to link. Here's the log:
Linking CXX static library
/Users/fcmo
On 8/10/07, Kyle Heath <[EMAIL PROTECTED]> wrote:
> I would like to use cmake to build a set of single target projects
> (each project generates either one library or one executable). I
> understand how to handle dependencies on external packages with the
> Find.cmake scripts, but I don't know how
I would like to use cmake to build a set of single target projects
(each project generates either one library or one executable). I
understand how to handle dependencies on external packages with the
Find.cmake scripts, but I don't know how to deal with internal
CMake built packages. There is som
2007/7/2, Alexander Neundorf <[EMAIL PROTECTED]>:
On Monday 02 July 2007 08:05, Jesper Eskilson wrote:
> Hi all,
>
> Is there a way to extract the list of library dependencies specified
> by target_link_libraries for a target? I would like to be able to pass
> the list of libraries to an externa
On Monday 02 July 2007 08:05, Jesper Eskilson wrote:
> Hi all,
>
> Is there a way to extract the list of library dependencies specified
> by target_link_libraries for a target? I would like to be able to pass
> the list of libraries to an external script at build time.
Does export_library_depende
On 2007-07-02 14:05+0200 Jesper Eskilson wrote:
Hi all,
Is there a way to extract the list of library dependencies specified
by target_link_libraries for a target? I would like to be able to pass
the list of libraries to an external script at build time.
For PLplot we deal with this problem
Hi all,
Is there a way to extract the list of library dependencies specified
by target_link_libraries for a target? I would like to be able to pass
the list of libraries to an external script at build time.
--
/Jesper
___
CMake mailing list
CMake@cmak
In 2.2 when you specified SET(CMAKE_VERBOSE_MAKEFILE ON) and then did
"make -s" you got some nice looking output of what you were building.
Now with 2.4 it's all pretty and colored (nice!), but whenever I link a
library I get what appears to be the contents of link.txt:
Linking CXX shared lib
95 matches
Mail list logo
