[CMake] suggested or best-practice for independent subproject library
Mateusz Loskot
mateusz at loskot.net
Sat Dec 14 14:34:31 EST 2013
(I'm picking up a few months old thread, which seems to have not received any
answer)
Jeet Sukumaran wrote
> I have a project that includes (and is dependent on) some independent
> sub-projects, e.g.
>
> "project1"/
> CMakeLists.txt
> src/
> library1/
> CMakeLists.txt
> include/
>
> <source files ...>
> src/
>
> <source files ...>
> main/
> CMakeLists.txt
>
> <source files ...>
> "library1" is actually maintained as a git submodule, and is included in a
> number of entirely different project, (e.g. "project2", "project3",
> etc.).
> Within each of these main or super projects like "project1", I want to
> just
> build the library1 and statically link programs to it as needed (i.e.,
> without installing library1's headers and binaries to the installation
> destination).
Jeet,
Have you managed to solve this task of combining use of git submodule
and exported targets without installation?
Anyone, is it even possible?
Best regards,
--
Mateusz Łoskot, http://mateusz.loskot.net
-----
--
Mateusz Loskot
http://mateusz.loskot.net
--
View this message in context: http://cmake.3232098.n2.nabble.com/suggested-or-best-practice-for-independent-subproject-library-tp7584404p7586363.html
Sent from the CMake mailing list archive at Nabble.com.
More information about the CMake
mailing list