#Unix cmake tutorial how to#
#Unix cmake tutorial update#

as if there were no nested project() statements). vgdbcmake project: If HideInnerProjectTargets is selected, all targets will be shown as if they were defined in the outer project (i.e. You can control how filtering works using the “Hide Redundant Targets” setting in the VS settings for the. As this is not very convenient, VisualGDB automatically hides redundant target instances. outer) project and once as a part of the including project. inner project) twice – once as a part of the including (a.k.a. If a CMake project includes another project, CMake would normally report the targets of the included project (a.k.a.See how it now shows 2 project nodes, one for each project() statement: Save the CMakeLists file and look at the Solution Explorer.

Open the CMakeLists.txt file from the subdirectory and add the following line there:

Now we will show how CMake handles subprojects.

See how the “Source Files” nodes have disappeared and the sources are shown directly under the target nodes:.

try setting the “Group Sources By Types” to “False”: You can use the settings in the “Sorting/Grouping” category to control how VisualGDB groups the sources or targets.

Open Visual Studio Properties for the project itself (.vgdbcmake node).

See how VisualGDB starts the selected target and how the command-line arguments match the ones set via Target Settings:.

Right-click on the main target and select Debug->Start a new instance to begin debugging it:.

Open the VS Project Properties (alt-Enter) for the main target and set the command-line arguments to a non-empty value: Build-related properties like include directories will be automatically saved to CMakeLists.txt files. Debug-related properties like command-line arguments will be stored in the project file itself.

Each CMake target under the VisualGDB CMake Project can have an independent set of properties.

This time add “subdir2” to the source file path:.

Add another source file to the new target:.

cpp file to the new target’s file (optionally replacing the hello message) and build the project:

VisualGDB will automatically create the “subdir” folder, put a CMakeLists.txt file there and reference it from the main CMakeLists file.

Then pick “Executable” and add “/subdir” to the location: vgdbcmake node in Solution Explorer and select Add->New Item. First we will create another executable target.

#Unix cmake tutorial how to#

Now we will show how to manage project targets and edit various settings using the GUI.

Set a breakpoint in main() and press F5 to ensure that you can debug the project:.

Once the project is created, press Ctrl-Shift-B to build your solution:.

The easiest way would be to proceed with the default settings of uploading the modified sources to the Linux machine: You can also configure VisualGDB to store the sources directly on the Linux machine and access them via SSH.

On the next page specify how should the Linux machine access the source code.

If you have not configured the connection to that computer with VisualGDB yet, follow the generic Linux tutorial to set it up.

On the next page select the Linux computer you want to target and press “Next”.On the first wizard page ensure that “Create a new project” is selected and then select the “Use CMake” and check the “Use the advanced CMake Project Subsystem” checkbox:.Select the Linux Project Wizard from VisualGDB folder: Start Visual Studio and open the “New Project” dialog.

#Unix cmake tutorial update#

This tutorial shows how to create, build and debug a simple CMake-based project with Visual Studio and use the Advanced CMake Project Subsystem to automatically update the CMakeLists.txt files when editing the project.īefore you begin, make sure that VisualGDB 5.3 or later is installed.