{"id":8861,"date":"2024-05-01T10:05:23","date_gmt":"2024-05-01T17:05:23","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=8861"},"modified":"2024-05-01T10:06:21","modified_gmt":"2024-05-01T17:06:21","slug":"importing-cmake-projects-using-presets","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/tutorials\/linux\/cmake\/import\/presets\/","title":{"rendered":"Importing CMake Projects using Presets"},"content":{"rendered":"

This tutorial shows how to import preset-based CMake projects into VisualGDB so that they can be developed in multiple IDEs simultaneously. We will create a basic C++ project for Raspberry Pi using CMake Presets, build it with VS code, and then import it into VisualGDB, showing how preset changes made in one IDE will immediately affect the other one.<\/p>\n

Before you begin, install VisualGDB 6.0R2 or later, our Raspberry Pi toolchain<\/a> and create a new folder with the following files:<\/p>\n

CMakeLists.txt<\/strong><\/p>\n

cmake_minimum_required(VERSION 3.5)\r\nproject(CMakePresetDemo)\r\nadd_executable(CMakePresetDemo CMakePresetDemo.cpp)<\/pre>\n
CMakePresetDemo.cpp<\/strong><\/p>\n
#include <iostream>\r\n\r\nint main(int argc, char *argv[])\r\n{\r\n    std::cout << \"Hello, World!\" << std::endl;\r\n    return 0;\r\n}<\/pre>\n
CMakePresets.json<\/strong><\/p>\n
{\r\n    \"version\": 4,\r\n    \"configurePresets\": [\r\n        {\r\n            \"name\": \"RaspberryPi\",\r\n            \"cacheVariables\": {\r\n                \"CMAKE_SYSTEM_NAME\": \"Linux\",\r\n                \"VISUALGDB_TOOLCHAIN_TYPE\": \"Linux\",\r\n                \"VISUALGDB_TOOLCHAIN_SUBTYPE\": \"GCC\",\r\n                \"CMAKE_C_COMPILER\": \"$env{TOOLCHAIN_ROOT}\/bin\/arm-linux-gnueabihf-gcc.exe\",\r\n                \"CMAKE_BUILD_TYPE\": \"Debug\",\r\n                \"CMAKE_SYSROOT\": \"$env{TOOLCHAIN_ROOT}\/arm-linux-gnueabihf\/sysroot\",\r\n                \"CMAKE_MAKE_PROGRAM\": \"$penv{VISUALGDB_DIR}\/ninja.exe\"\r\n            },\r\n            \"environment\": {\r\n                \"TOOLCHAIN_ROOT\": \"C:\/SysGCC\/raspberry\",\r\n                \"PATH\": \"C:\/SysGCC\/raspberry\/bin;$penv{PATH}\"\r\n            },\r\n            \"binaryDir\": \"${sourceDir}\/build\/${presetName}\",\r\n            \"generator\": \"Ninja\"\r\n        }\r\n    ]\r\n}<\/pre>\n
Note how the CMakeLists.txt<\/strong> file specifies the project structure (application consisting of 1 C++ file), but the actual toolchain and the location of various tools (e.g. Ninja) comes from the preset file.<\/p>\n
    \n
  1. Open the project folder in Visual Studio Code. Press Ctrl-Shift-P and locate the “CMake:Configure<\/strong>” command:\"\"<\/a><\/li>\n
  2. Pick the RaspberryPi<\/strong> preset:\"\"<\/a><\/li>\n
  3. VS Code will automatically configure the project based on the preset file, and will allow building it:
    \n    \"\"<\/a><\/li>\n
  4. Now we will show how to import that project into VisualGDB reusing the same preset file. Start Visual Studio and locate the VisualGDB Linux Project Wizard:
    \n    \"\"<\/a><\/li>\n
  5. Enter the name and location for the imported project file:\"\"<\/a>Note that the actual build settings are stored in the preset file shared with VS code. The imported project file will only contain the debug settings.<\/li>\n
  6. On the first page of the wizard, select Import a project -> Import a CMake Project<\/strong>:\"\"<\/a><\/li>\n
  7. Select”Build the project locally with a cross-compiler” and pick the Raspberry Pi toolchain:\"\"<\/a>The toolchain selected in the wizard will be only used to locate the GDB debugger. Actual build settings and IntelliSense configuration will come from the preset file. If you do not want to import your actual toolchain into VisualGDB, you can pick any toolchain here and simply override the GDB path via VisualGDB Project Properties<\/strong> later.<\/li>\n
  8. On the last page of the wizard select the location of the CMakeLists.txt<\/strong> file and ensure that the “Use existing presets” checkbox is checked:
    \n    \"\"<\/a><\/li>\n
  9. Press “Finish”<\/strong> to import the project into Visual Studio. Note how the RaspberryPi preset got translated into a Solution-level configuration: \"\"<\/a><\/li>\n
  10. Open VisualGDB Project Properties and click the “Manage” button near the configuration selector. In the preset editor click “Create a new configuration preset”:\"\"<\/a><\/li>\n
  11. Create a new preset called RaspberryPi-Release<\/strong> inheriting the regular RaspberryPi<\/strong> preset:\"\"<\/a><\/li>\n
  12. Change the build type for the new preset to RelWithDebInfo <\/strong>(you would need to click the edit button first):\"\"<\/a><\/li>\n
  13. Press OK to commit the changes. Note how VisualGDB created a new solution configuration matching the new preset:\"\"<\/a><\/li>\n
  14. Reopen the folder in VS Code. Note how it picked up the new preset allowing you to configure and build the project with it:
    \n    \"\"<\/a><\/li>\n
  15. Add another preset on the VS Code side, inheriting from either of the presets: \"\"<\/a><\/li>\n
  16. Enter a different name for it and commit it by pressing Enter:\"\"<\/a><\/li>\n
  17. VS Code will automatically edit the CMakePresets.json<\/strong> file, adding the new preset:
    \n    \"\"<\/a><\/li>\n
  18. Go back to Visual Studio and reopen the solution. VisualGDB will detect the new preset, suggesting to create a configuration for it:\"\"<\/a><\/li>\n
  19. Once you select “Create”, VisualGDB will create another solution configuration matching the preset created in VS Code:\"\"<\/a><\/li>\n<\/ol>\n
    Because both IDEs are using CMake to manage the actual build, you can edit various project settings (e.g. add new files, change include directories), etc. in either of them, and the other IDE will pick up the changes as long as you reload the project.<\/p>\n","protected":false},"excerpt":{"rendered":"
    This tutorial shows how to import preset-based CMake projects into VisualGDB so that they can be developed in multiple IDEs<\/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,41],"_links":{"self":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/8861"}],"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=8861"}],"version-history":[{"count":2,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/8861\/revisions"}],"predecessor-version":[{"id":8883,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/8861\/revisions\/8883"}],"wp:attachment":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/media?parent=8861"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/categories?post=8861"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/tags?post=8861"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}