{"id":2934,"date":"2017-07-13T10:22:43","date_gmt":"2017-07-13T17:22:43","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=2934"},"modified":"2017-08-10T16:33:24","modified_gmt":"2017-08-10T23:33:24","slug":"organizing-and-reusing-cc-library-projects-with-cmake","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/tutorials\/linux\/cmake\/library\/","title":{"rendered":"Organizing and Reusing C\/C++ Library Projects with CMake"},"content":{"rendered":"

This tutorial shows how to create library projects with CMake and reference the from other projects. We will create a basic shared library for Raspberry Pi using a cross-toolchain, make it export a few settings and import it from a different project.<\/p>\n

Before you begin, install VisualGDB 5.3 or later.<\/p>\n

    \n
  1. Start Visual Studio and open the VisualGDB Linux Project Wizard:\"01-prjname\"<\/a><\/li>\n
  2. Select “Create a new project -> Application -> Use CMake” and check the “Use the advanced CMake Project System” checkbox:\"02-cmakesys\"<\/a>We will change the project type to a shared library once the project is created.<\/li>\n
  3. On the next page select “Build the project locally with a cross-compiler” and pick the “Raspberry Pi” cross-toolchain. If it’s not installed, VisualGDB will download and install it automatically. Then select your Raspberry Pi in the “Development computer” field:\"03-target\"<\/a><\/li>\n
  4. Press “Finish” to generate the project. Open the generated CMakeLists.txt file and find the add_executable() statement:\"04-prj\"<\/a><\/li>\n
  5. Replace “add_executable(…)” with “add_library(<name> SHARED <…>)” and save the CMakeLists.txt file so that Solution Explorer picks up the update. Then right-click on the “Source files” folder and select “Add->New Item”:\"05-newitem\"<\/a><\/li>\n
  6. Add the following files to the library:\n
      \n
    1. private\/PrivateHeader.h:\n
      #pragma once\r\n#include <stdio.h>\r\n\r\nstatic void PrivateFunction()\r\n{\r\n\u00a0\u00a0\u00a0 printf(\"Hello from PrivateFunction()\\n\");\r\n}<\/pre>\n<\/li>\n
    2. public\/PublicHeader.h:\n
      #pragma once\r\n\r\nvoid PublicFunction();<\/pre>\n<\/li>\n
    3. Replace the main source file contents with this:\n
      #include \"PrivateHeader.h\"\r\n#include \"PublicHeader.h\"\r\n\r\n#ifdef USING_CMAKE_LIBRARY_DEMO\r\n#error This should not happen\r\n#endif\r\n\r\nvoid PublicFunction()\r\n{\r\n\u00a0\u00a0\u00a0 printf(\"Hello from PublicFunction()\\n\");\r\n\u00a0\u00a0\u00a0 PrivateFunction();\r\n}<\/pre>\n
      This illustrates the concept of public and private header files. Private headers are headers only visible to the library itself. Public headers are headers visible to any program that uses the library and typically contain declarations for exported library functions.<\/li>\n<\/ol>\n<\/li>\n
    4. As we have not set any include directories, the PrivateHeader.h and PublicHeader.h files will appear as missing:\"06-includes\"<\/a><\/li>\n
    5. Open Visual Studio properties for the library and add “private” to the Additional Include Directories field:\"07-private\"<\/a><\/li>\n
    6. Then add “public” to the Exported Settings -> Public -> Additional Include Directories:\"08-public\"<\/a><\/li>\n
    7. Finally add “USING_CMAKE_LIBRARY_DEMO” to the Exported Settings->Interface->Preprocessor Definitions:\"09-iface-macro\"<\/a>The difference between Public and Interface settings is that Public<\/strong> settings are applied to both the library and the applications using it, while the Interface<\/strong> settings are only applied to the library users. I.e. the USING_CMAKE_LIBRARY_DEMO macro will not be defined when compiling the library itself.<\/li>\n
    8. Apply the settings and ensure that CMakeLists.txt got edited accordingly:\"10-cmakelists\"<\/a><\/li>\n
    9. The main source file should now compile without problems:\"11-build\"<\/a><\/li>\n
    10. Now we show how to use the library from other projects. First we will add a small demo application to the same CMake project. Then we will show how to import the library from a different project. Right-click in the .vgdbcmake project item and select Add->New Item. Then pick “Executable”:\"12-client\"<\/a><\/li>\n
    11. Replace the main file contents for the newly created executable with this:\n
      #include \"PublicHeader.h\"\r\n\r\n#ifndef USING_CMAKE_LIBRARY_DEMO\r\n#error CMakeLibraryDemo is missing\r\n#endif \r\n\r\nint main()\r\n{\r\n\u00a0\u00a0\u00a0 PublicFunction();\r\n\u00a0\u00a0\u00a0 return 0;\r\n}<\/pre>\n<\/li>\n
    12. Note that initially the PublicHeader.h won’t be found: \"13-clientsrc\"<\/a><\/li>\n
    13. Right-click on the References node in Solution Explorer and add a reference from the test application to CMakeLibraryDemo:\"14-addref\"<\/a><\/li>\n
    14. Now the test application should build properly. Try debugging it by pressing F5:\"15-run\"<\/a><\/li>\n
    15. Note how both DemoLibraryClient and libCMakeLibraryDemo.so got deployed to \/tmp on your Raspberry Pi. You can change the deployment directory for the entire project via Visual Studio Project Properties for the .vgdbcmake project in Solution Explorer. Try changing it to \/tmp\/MyLibraryDemo:\"16-deploy\"<\/a><\/li>\n
    16. Now both the library and the application will be deployed to the new directory:\"17-newpath\"<\/a><\/li>\n
    17. Now we will show how to reference the library from a completely different project. Start the VisualGDB Linux Project Wizard again and create another CMake-based application in a different directory:\"anotherclient\"<\/a><\/li>\n
    18. Replace the main source file contents with this:\n
      #include <stdio.h>\r\n\r\n#ifdef USING_CMAKE_LIBRARY_DEMO\r\n#include \"PublicHeader.h\"\r\n#endif \r\n\r\n\r\nint main(int argc, char *argv[])\r\n{\r\n#ifdef USING_CMAKE_LIBRARY_DEMO\r\n\u00a0\u00a0\u00a0 PublicFunction();\r\n#else\r\n\u00a0\u00a0\u00a0 printf(\"Compiled without CMakeLibraryDemo\\n\");\r\n#endif \r\n}<\/pre>\n<\/li>\n
    19. As we have not referenced the library yet, the part printing “Compiled without CMakeLibraryDemo” will be active:\"19-clientsrc\"<\/a><\/li>\n
    20. Before we can reference the library from this project, we need to add a reference to the corresponding CMakeLists.txt file. Right-click on the .vgdbcmake project in Solution Explorer and select Add->Reference Another CMake Folder:\"20-addref\"<\/a><\/li>\n
    21. Point to the CMakeLists.txt file belonging to the library project:\"21-pickfile\"<\/a><\/li>\n
    22. This will insert an “add_subdirectory” statement to the new project’s CMakeLists.txt file referencing the library project’s directory:\"22-sln\"<\/a><\/li>\n
    23. Save the CMakeLists.txt file to update Solution Explorer. Now you can add a reference to CMakeLibraryDemo using the normal Add Reference<\/strong> command:\"23-addref\"<\/a><\/li>\n
    24. Build the project and see how PublicFunction()<\/strong> is now invoked:\"24-deployed\"<\/a><\/li>\n
    25. The “add reference” command translated to adding CMakeLibraryDemo to the target_link_libraries() statement in CMakeLists.txt:\"25-link\"<\/a>Once we did that, CMake automatically picked up the USING_CMAKE_LIBRARY_DEMO macro and the public include directory from the exported settings in the library project, so we did not need to specify them by hand.<\/li>\n<\/ol>\n
      Note that each time you build the project, CMake will check the dependencies of the CMakeLibraryDemo project and build it if needed. If your library project is too complicated and you want to avoid rechecking\/building it each time, consider creating a CMake package. See this tutorial<\/a> for a detailed example on using packages.<\/p>\n","protected":false},"excerpt":{"rendered":"
      This tutorial shows how to create library projects with CMake and reference the from other projects. We will create a<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10],"tags":[77,79,33,85],"_links":{"self":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/2934"}],"collection":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/comments?post=2934"}],"version-history":[{"count":3,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/2934\/revisions"}],"predecessor-version":[{"id":3024,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/2934\/revisions\/3024"}],"wp:attachment":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/media?parent=2934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/categories?post=2934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/tags?post=2934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}