{"id":5877,"date":"2020-04-03T12:55:49","date_gmt":"2020-04-03T19:55:49","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=5877"},"modified":"2020-10-22T13:37:20","modified_gmt":"2020-10-22T20:37:20","slug":"visualgdb-project-type-overview","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/documentation\/projects\/overview\/","title":{"rendered":"VisualGDB Project Type Overview"},"content":{"rendered":"

Overview<\/h2>\n

This page provides an overview of various VisualGDB project types. We will explain the advantages and limitations of those types, and will show how to understand the type of your existing project. You can find an overview of the most commonly used project types below:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Project Type<\/td>\nSupported Targets<\/td>\nBuild Settings Stored in<\/td>\nBuild Managed by<\/td>\nTools Needed to Build<\/td>\n<\/tr>\n
MSBuild<\/a><\/td>\nEmbedded, Linux<\/td>\n.vcxproj<\/strong> file<\/td>\nMSBuild + VisualGDB<\/td>\nVisual Studio + VisualGDB<\/td>\n<\/tr>\n
Legacy GNU Make<\/a><\/td>\nEmbedded, Linux, Android, MinGW\/Cygwin<\/td>\nMakefile<\/td>\nGNU Make<\/td>\nGNU Make<\/td>\n<\/tr>\n
Advanced CMake<\/a><\/td>\nEmbedded, Linux, Windows (import only), Android<\/td>\nCMakeLists.txt<\/td>\nCMake<\/td>\nCMake, Ninja\/Make<\/td>\n<\/tr>\n
Legacy QMake and CMake<\/a><\/td>\nLinux<\/td>\n<\/td>\nQMake\/CMake<\/td>\nQMake\/CMake<\/td>\n<\/tr>\n
Custom Imported<\/a><\/td>\n<\/td>\nexternal files<\/td>\nexternal tools<\/td>\nexternal tools<\/td>\n<\/tr>\n
Advanced Mbed<\/a><\/td>\nMbed<\/td>\nmbed_app.json<\/td>\nmbed-cli<\/td>\npython, mbed<\/td>\n<\/tr>\n
Advanced Arduino<\/a><\/td>\nArduino<\/td>\n.vgdbproj<\/strong> file<\/td>\narduino-builder.exe<\/td>\nArduino Build Tools<\/td>\n<\/tr>\n
Advanced ESP-IDF<\/a><\/td>\nESP32<\/td>\ncomponent.mk\/CMakeLists.txt<\/td>\nESP-IDF<\/td>\nESP-IDF, CMake, Ninja<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The legacy<\/strong> project types work by creating a VC++ project on top of the actual build scripts (e.g. Makefile<\/strong> or CMakeLists.txt<\/strong>). VisualGDB updates the underlying scripts to reflect files added via Solution Explorer, but the rest of the build settings are disconnected from the Visual Studio GUI (most can be edited via VisualGDB Project Properties).<\/p>\n

The advanced<\/strong> projects query the exact project structure from the underlying build system (e.g. Arduino or CMake) and render it in Solution Explorer. VisualGDB fully controls the contents of Solution Explorer for those projects and provides convenient commands and settings windows for editing various common settings.<\/p>\n

<\/a>MSBuild<\/h2>\n

The MSBuild-based projects are very similar to the regular VC++ Windows projects. VisualGDB provides its own highly optimized backend for the MSBuild system, supporting GCC, Clang IAR and Keil compilers. You can tell an MSBuild-based project by the “VisualGDB<\/strong>” platform name in Configuration Manager and<\/strong> the regular VC++ project icon: \"\"<\/a>VisualGDB fully controls the build process of MSBuild-based projects and allows tweaking it via numerous settings in the regular VS properties windows. You can find a detailed description of the MSBuild projects on this page<\/a>.<\/p>\n

MSBuild-based projects support most properties and features of the regular Win32 projects: property sheets, per-configuration settings, custom targets, etc. We recommend using them for all new Embedded projects. If you are familiar with Visual Studio and VC++, we also recommend using MSBuild for Linux projects. Otherwise, please consider Advanced CMake<\/a>.<\/p>\n

Note that MSBuild-based projects do not support the ESP32<\/strong> devices, as they come with their own SDK (ESP-IDF). If you are targeting an ESP32 device, please use the Advanced ESP-IDF Project Subsystem<\/a> instead.<\/p>\n

<\/a>Legacy GNU Make<\/h2>\n

The GNU Make-based projects consist of a Makefile containing the actual build settings, and a dummy VC++ project that hands over the build logic to VisualGDB.exe<\/strong>. You can tell a GNU Make-based project (and other legacy projects) by the “x86<\/strong>” or “Win32<\/strong>” platform name and the regular VC++ project icon:\"\"<\/a>VisualGDB, in turn, launches GNU Make, that handles the build.<\/p>\n

You can edit most build settings of GNU Make projects via VisualGDB Project Properties:\"\"<\/a>Any changes made here will be saved to the Makefile, and the IntelliSense settings of the dummy VC++ project will be updated accordingly. Note that this only works for Makefiles created with VisualGDB (that follow the VisualGDB Makefile structure).<\/p>\n

This project type is recommended if you are familiar with GNU Make and are planning to extend the Makefile with custom targets. For all other scenarios, please consider using Advanced CMake<\/a> or MSBuild<\/a> instead.<\/p>\n

<\/a>Advanced CMake<\/h2>\n

Advanced CMake projects are thin wrappers on top of the CMakeLists.txt<\/strong> files. The build settings for CMake projects are stored in the CMakeLists.txt<\/strong> files, allowing the projects to be built on any machine that has CMake installed. VisualGDB provides convenient GUI for most commonly used CMake settings and will automatically edit CMakeLists.txt<\/strong> when you change them. You can tell an Advanced CMake project by the CMake<\/strong> icon in Solution Explorer:\"\"<\/a>Advanced CMake projects support multiple targets per project (e.g. executable + static library), allow stepping through CMakeLists.txt files<\/a> and are generally recommended over other project types, as long as your platform is supported.<\/p>\n

Starting from VisualGDB 5.5, the Advanced CMake Project Subsystem fully supports embedded projects. See this page<\/a> for detailed documentation on them.<\/p>\n

<\/a>Legacy QMake and CMake<\/h2>\n

The legacy QMake and CMake projects are similar to the GNU Make-based projects<\/a>, having the same advantages and disadvantages:\"\"<\/a>We generally do not recommend them for new projects, unless you need compatibility with earlier VisualGDB versions.<\/p>\n

<\/a>Custom Imported Projects<\/h2>\n

This project type is used for existing complex projects that are not based on CMake and do not follow the VisualGDB Makefile layout. You can create it by selecting the generic “Import” option in either Embedded or Linux project wizard:\"\"<\/a>Custom imported projects are very similar to the Legacy projects. Unlike GNU Make projects, VisualGDB does not make any assumptions about the underlying build system. It will simply launch the build\/clean command line specified via VisualGDB Project Properties and will assume that it produced the binary specified in the “Main binary” field:\"\"<\/a>For this type of project, VisualGDB will not automatically update the IntelliSense settings, so you would need to configure IntelliSense manually via VisualGDB Project Properties.<\/p>\n

We recommend using this type to quickly import existing large projects into VisualGDB without converting any settings. You will be instantly able to build and debug the project, although IntelliSense will not be precise, and changing build settings would require manually editing your existing Make files. Once you get comfortable with VisualGDB, we advise converting your project to CMake and using the Advanced CMake Project Subsystem<\/a> with it.<\/p>\n

<\/a>Advanced Mbed<\/h2>\n

Advanced Mbed projects work by integrating the mbed-cli<\/strong> tools into Visual Studio. VisualGDB lets mbed handle the actual build of the project, discovers the underlying project structure and renders it in Solution Explorer, allowing you to tweak various build parameters:\"\"<\/a>Advanced Mbed projects can support multiple targets (i.e. boards) that can be added via the Add->Manage mbed Boards<\/strong> command in Solution Explorer.<\/p>\n

You can build Advanced Mbed projects outside VisualGDB by running the build command shown in the VisualGDB Build window. This will produce the same results as building the project with VisualGDB.<\/p>\n

We recommend using Mbed (and the Advanced Mbed Project System) if you are targeting one of the platforms supported by mbed and would like to take advantage of the libraries included with the Mbed OS. Another good use for Mbed would be to create portable projects that can simultaneously target multiple boards supported by mbed.<\/p>\n

<\/a>Advanced Arduino<\/h2>\n

Advanced Arduino projects work by integrating the Arduino Build system (arduino-builder.exe<\/strong>) into Visual Studio. They use the same build logic and produce the same results as Arduino IDE. VisualGDB supports the regular Arduino targets as well as the ESP32, ESP8266, STM32 and Bluno M3 Arduino cores. The project structure shown in Solution Explorer is queried directly from the Arduino build tools and hence 100% matches the built project:\"\"<\/a>VisualGDB also supports numerous Arduino libraries and packages that can be managed via Tools->VisualGDB->Manage VisualGDB Packages<\/strong>.<\/p>\n

We recommend using Arduino projects for quick prototyping, or if you would like to use a specific Arduino-based library. As most settings for Arduino projects are automatically guessed by the Arduino build system, the initial setup is considerably easier, compared to other project types. That said, the auto-detection of settings makes it harder to tweak and understand the build process, so if you are planning a large project, please consider using MSBuild<\/a> instead.<\/p>\n

For more information see our documentation on the Advanced Arduino Project Structure<\/a>.<\/p>\n

<\/a>Advanced ESP-IDF<\/h2>\n

The Advanced ESP-IDF projects are specifically designed to integrate the ESP-IDF framework<\/a> into Visual Studio. They are based on the Advanced CMake<\/a> projects and render the detailed and precise structure of your project (including the ESP-IDF framework) in Solution Explorer, providing numerous commands and settings pages for controlling most commonly used settings:\"\"<\/a>If you are targeting an ESP32 device (or an ESP8266 device with RTOS SDK 3.0+) and do not want to use the Arduino core, the Advanced ESP-IDF project type is the project type to use.<\/p>\n

For more information, see our documentation on Advanced ESP-IDF Project Structure<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Overview This page provides an overview of various VisualGDB project types. We will explain the advantages and limitations of those<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[201],"tags":[],"_links":{"self":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/5877"}],"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=5877"}],"version-history":[{"count":6,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/5877\/revisions"}],"predecessor-version":[{"id":7047,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/5877\/revisions\/7047"}],"wp:attachment":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/media?parent=5877"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/categories?post=5877"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/tags?post=5877"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}