, 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
We use similar layout in a set of components, but in order to do that we just
store library interface headers in lib-name/include/lib-name directory. And
layout of library directory is the following:
src/ - internal headers and implementation
include/ - external headers
CMakeLists.txt
Then you
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 install-prefix/include/graphviz and
