[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cmake
Subject:    Re: [CMake] Build application suite with dependency checking but single shared libraries without it
From:       felix <felix.schwitzer () gmx ! at>
Date:       2013-12-01 21:25:42
Message-ID: 1385933142454-7586232.post () n2 ! nabble ! com
[Download RAW message or body]

I think your use case is a common one. You can split up all things in
different projects and use
a superproject and using ExternalProject, but maybe that needs a big rework
of your project structure.

I have in my repository also a lot of libraries and some applications and
use the export command to
allow other projects to import the library. Let me explain with a example
what I mean. Suppose I have
a structure like
- lib1
- lib2
- myapp
where myapp depends on lib1 and lib2, lib2 depends on lib1.
When generating lib1 export the cmake-configuration and then in lib2 simply
use

set(lib1_DIR "../lib1)
find_package(lib1 REQUIRED)

regards
Felix



--
View this message in context: \
http://cmake.3232098.n2.nabble.com/Build-application-suite-with-dependency-checking-but-single-shared-libraries-without-it-tp7586228p7586232.html
 Sent from the CMake mailing list archive at Nabble.com.
--

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 to support the CMake community. For more \
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at \
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake


[prev in list] [next in list] [prev in thread] [next in thread]