Hei hei,
for a standalone build without system libraries I was experimenting
with the ExternalProject module today. My goal is to have some top
level build project which includes several CMake projects and some
external projects without relying on dev libraries installed on the
system (reason are
Hei hei,
On 13.12.2014 09:08, ambreen haleem wrote:
> In my main repository where my project reside, I created a sub-directory
> called build. When I do cmake -G "KDevelop3", I do get a kdevelop project
> in the build but it has no src files and most of the files in there are
> cmake related. I'm
Hei hei,
On Fri, May 17, 2013 at 11:09:11AM -0400, Robert Maynard wrote:
> - target_link_libraries(myexe yourlib) can now build myexe sources
> with requirements specified
Does this mean transitive linking between separate projects is possible?
Greets
Alex
--
»With the first link, the chain
Hei hei,
On Mon, May 13, 2013 at 06:17:58PM -0400, Matthew Woehlke wrote:
> Another option to consider is keeping the file in an external
> repository and using your VCS's external-repo support to bring it
> into your other projects. This way the file exists in your source
> tree, but your VCS is
Hello Michael,
Am 2012-03-06 16:46, schrieb Michael Hertling:
> or possibly better:
>
> # libbar/bar-config.cmake.in:
> FIND_PACKAGE(FOO PATHS @FOO_DIR@ NO_DEFAULT_PATH)
I used
FIND_PACKAGE(FOO 0.1.0 REQUIRED)
in the package config file now, which works, too.
> BTW, find modules / config fil
Hei hei,
we faced a build problem with transitive linking of separate projects
where I can't find the right solution on my own. I hope someone can give
me a hint. I prepared a test case with two libraries libfoo and libbar
and an application baz. libfoo is on his own, libbar calls a function
from
Hei hei,
On Wed, 21 Sep 2011 16:42:37 +0200, Alexander Dahl wrote:
>> The foo-targets.cmake file contains "foo-shared" as imported target,
>> and it is this name that must be supplied to TARGET_LINK_LIBRARIES().
>> Besides, the DESTINATION clause of INSTALL() should
Hei hei,
On Tue, 20 Sep 2011 16:38:06 +0200, Michael Hertling wrote:
> This leaves the target named "foo-shared", not "foo"; the latter is
> just the base name of the target's disk file, i.e. libfoo.so.0.1.0.
It does.
> The foo-targets.cmake file contains "foo-shared" as imported target,
> and i
Hello there,
after using FindFOO.cmake scripts for our own projects for a long time
I'm trying to migrate this to the "real" CMake approach of package
configuration files. Therefor I read chapter 5.7 of the book »Mastering
CMake« and two HowTos [1] [2] on the web merging all of these in some
file
Hello,
we use CMake to build several libraries and applications for an
embedded Linux target with a cross compile toolchain. Recently we
separated this from one huge source tree to one standalone project for
each library and application, each in its own Git repository. The
classical approach for
10 matches
Mail list logo
