#CMAKE LIBRARY PATH INSTALL#
#CMAKE LIBRARY PATH CODE#

Why is that, why is it different from the way in was included in external project? Well, it is because that is how this header is placed in the libraryвЂ™s source include folder - there is no SomeLibrary folder nested there.

#CMAKE LIBRARY PATH CODE#

While the code here is the same as the one from external project, there is one notable difference - some.h is not prepended with SomeLibrary/ in the #include statement. Std ::cout << 'base application message' << std ::endl #include #include int main( int argc, char *argv) Now letвЂ™s see how your users or yourself can link to the library.

#CMAKE LIBRARY PATH INSTALL#

So there you have it! The library has been successfully built and nicely installed, so now you can just zip the install folder contents and distribute it to your users. Installing: /Users/YOURNAME/code/cpp/someLibrary/install/cmake/SomeLibrarењњonfig-release.cmake Up-to-date: /Users/YOURNAME/code/cpp/someLibrary/install/include/SomeLibrary/some.h Install configuration: 'Release' - Installing: /Users/YOURNAME/code/cpp/someLibrary/install/lib/libSomeLibrary.a Installing: /Users/YOURNAME/code/cpp/someLibrary/install/cmake/SomeLibrarењњonfig-debug.cmake Install configuration: 'Debug' - Installing: /Users/YOURNAME/code/cpp/someLibrary/install/lib/libSomeLibraryd.a Linking CXX static library libSomeLibraryd.a This is because we ran configuration without specifying the build type - better to explicitly set it then, both Debug and Release:

Note that SomeLibrarењњonfig-noconfig.cmake has this weird noconfig suffix. Installing: /Users/YOURNAME/code/cpp/someLibrary/install/cmake/SomeLibrarењњonfig-noconfig.cmake Installing: /Users/YOURNAME/code/cpp/someLibrary/install/cmake/SomeLibrarењњonfig.cmake Installing: /Users/YOURNAME/code/cpp/someLibrary/install/include/SomeLibrary/some.h Install configuration: '' - Installing: /Users/YOURNAME/code/cpp/someLibrary/install/lib/libSomeLibrary.a Linking CXX static library libSomeLibrary.a Building CXX object CMakeFiles/SomeLibrary.dir/src/ Scanning dependencies of target SomeLibrary Configuring done - Generating done - Build files have been written to: /Users/YOURNAME/code/cpp/someLibrary/build Will set it to /Users/YOURNAME/code/cpp/someLibrary/install Detecting CXX compile features - done - This project is a top-level one Detecting CXX compiler ABI info - done - Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ - skipped Detecting C compile features - done - Detecting CXX compiler ABI info Detecting C compiler ABI info - done - Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc - skipped The CXX compiler identification is AppleClang 12.0032

The C compiler identification is AppleClang 12.0032 Having it, if you now try to find your package in external project ( cmake-library-example/external-project/CMakeLists.txt) like this: The write_basic_package_version_file() function from above will create SomeLibrarењњonfigVersion.cmake file in the install folder. Knowing that, hereвЂ™s how you can check if you are in the top-level project or not: This variable persists across all the nested projects, and so calling project command from nested projects will not change CMAKE_PROJECT_NAME, but will set another variable called PROJECT_NAME. It stores the top-level project name that you set with project command. In CMake projects there is a variable called CMAKE_PROJECT_NAME. So letвЂ™s gradually create a CMakeLists.txt for the library project.

will you need to have it as DLL on WindowsД®verything from this list is handled by CMake.

when its sources are nested in their source tree.

when they are using it pre-built as an external dependency.

how other applications can find the library.

where install artifacts should be placed.

what artifacts should the library produce at install step.

Here are some of the things you need to take care of: But doing just that would be too easy, wouldnвЂ™t it. Making a library with CMake is not that different from making an application - instead of add_executable you call add_library. #include const std ::string someString = 'some string' CMakeLists

Cmake library path