![\"structure\"](\"https:\/\/sysprogs.com\/w\/wp-content\/uploads\/2017\/06\/structure.png\")
<\/a><\/p>\nThis makes it possible to define advanced settings for each target (e.g.\u00a0where and when to deploy it or which command-line arguments to use when debugging it): So how do we get to not editing the CMakeLists.txt files manually when adding or removing sources or targets? CMake doesn’t normally let you do that, but if you look closer into\u00a0its sources you can actually see that it internally tracks\u00a0where each target is defined:<\/p>\n Even better, CMake actually remembers\u00a0the locations of all statements like target_link_libraries()<\/strong> that affect each target and lets its components query them:<\/p>\n So we made a very small modification to the CMake sources (see the commit in our CMake fork on Github<\/a>) that lets CMake report where exactly is each\u00a0target defined and list all statements like target_link_libraries() that affected the target.<\/p>\n This information\u00a0was just enough for VisualGDB to automatically edit the\u00a0add_executable()<\/strong> or add_library()<\/strong> statement\u00a0each time you add, remove or rename a source file: It will also recognize\u00a0the cases where the sources (or source subdirectories) are defined via variables and will use the same variables when adding new source files:<\/p>\n Renaming and deleting of targets and source files will also work completely automatically.<\/p>\n Another common scenario is editing target properties (e.g. adding new\u00a0include directories or\u00a0preprocessor macros).\u00a0To make this easier, we connected the regular Visual Studio property pages with the\u00a0underlying CMake statements. E.g. you can select one or more targets, open Properties and set Additional Include Directories for them: VisualGDB will then ask CMake for the location of all target_include_directories<\/strong> statements related to the selected targets and will edit them or create new ones if none were found:<\/p>\n This works in both directions: if you manually\u00a0add or edit similar statements in CMakeLists.txt files, VisualGDB will still recognize them, display their contents in VS property pages and let you edit them.<\/p>\n As the new CMake project subsystem works independently from the regular\u00a0Visual C++ projects\u00a0and all file and IntelliSense operations are under VisualGDB’s control,\u00a0the\u00a0sources don’t have to be physically located on the Windows machine anymore. So we added a special mode that\u00a0lets you create (or import) CMake projects directly on the Linux machine without setting up any shared folders: Because the\u00a0project structure used by VisualGDB is accurately reported by CMake and does not rely on any\u00a0specific\u00a0layout of the CMakeLists.txt files, the new CMake Project Subsystem\u00a0supports\u00a0opening\u00a0huge 3rd-party projects as long as they are based on CMake. VisualGDB will locate and display the targets, sources and settings the same way as for projects created from scratch: When combined\u00a0with the direct SSH file access,\u00a0this lets you\u00a0quickly open any CMake-based project on your Linux machine from\u00a0Visual Studio and\u00a0immediately begin developing it as if it was a normal\u00a0Windows project. We have also added a special diagnostics console that shows the internal status of the cache and calculates the exact time spent on fetching\u00a0files and listing directories on the Linux machine to make timing analysis easier: The new CMake Project Subsystem is available in the latest VisualGDB 5.3 Preview 1<\/a>.\u00a0Try it out with your CMake projects and we’ll be excited to hear your feedback via our support page<\/a> or forum<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" CMake has been getting increasingly popular over the past years due to\u00a0its simplicity and integration with the modern IDEs.\u00a0The recently added CMake Server mode made it even more usable, allowing it to share the precise project structure with different IDEs, but if you wanted to actively edit a large project, you would still inevitably have … Continue reading Introducing the new Advanced CMake Project Subsystem<\/span> <\/a>This also allowed us to automatically determine the exact list of libraries that are required by the currently debugged target, so VisualGDB can automatically deploy them and set variables like LD_LIBRARY_PATH<\/strong> and solib-search-path<\/strong> to make debugging work out-of-the-box.<\/p>\nEditing Projects<\/h2>\n
\/** Get a backtrace from the creation of the target. *\/\r\n cmListFileBacktrace const& GetBacktrace() const;<\/pre>\n
cmBacktraceRange GetIncludeDirectoriesBacktraces() const;\r\n cmBacktraceRange GetCompileOptionsBacktraces() const;\r\n cmBacktraceRange GetCompileFeaturesBacktraces() const;\r\n cmBacktraceRange GetCompileDefinitionsBacktraces() const;<\/pre>\n
<\/a>We made it as non-intrusive as possible, so it actually detects your formatting style like the maximum amount of\u00a0source items per line and follows it\u00a0when editing CMakeLists.txt:<\/a><\/p>\nTo make creation of new targets easier, we have added an option to create them from GUI as well. VisualGDB will automatically add the necessary statements\u00a0(and create\/reference new CMakeLists.txt files if you are creating targets in new subdirectories):<\/a><\/p>\nEditing Target Properties<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\nEditing Linux Projects via SSH<\/h2>\n
<\/a>Visual Studio will\u00a0recognize the special vgdb-ssh:\/\/… URLs and let VisualGDB handle them, while the rest of the Visual Studio will treat those files as if they were located on the Windows machine.\u00a0To avoid downloading the same files over and over, VisualGDB caches them locally and periodically\u00a0determines if any of them are outdated by running the “ls” command in the background. This results in\u00a0great performance and\u00a0extremely accurate\u00a0IntelliSense – it will understand Linux paths and will always use the latest versions of the headers:<\/a><\/p>\nImporting Existing Projects<\/h2>\n
<\/a><\/p>\n<\/a><\/p>\nTry it out<\/h2>\n