C/C++ for Visual Studio Code

For users of MinGW on Windows running extension version 0.16.1 or earlier, you must manually configure c_cpp_properties.json to ensure IntelliSense works correctly.

Key requirements:

1. intelliSenseMode: Set this to clang-x64.
2. includePath: You must include the specific system header paths used by your MinGW installation. You can find the correct paths by running gcc -v -E -x c++ nul in your terminal.
3. defines: You must define __GNUC__=# where # is the major version of your installed toolchain (e.g., __GNUC__=6).
4. Version Matching: Ensure all paths in includePath and browse.path match your specific MinGW version number (e.g., changing 6.3.0 to your installed version).

To create this file, select C/Cpp: Edit Configurations from the VS Code command palette.

{
    "configurations": [
        {
            "name": "MinGW",
            "intelliSenseMode": "clang-x64",
            "includePath": [
                "${workspaceRoot}",
                "C:/MinGW/lib/gcc/mingw32/6.3.0/include/c++",
                "C:/MinGW/lib/gcc/mingw32/6.3.0/include/c++/mingw32",
                "C:/MinGW/lib/gcc/mingw32/6.3.0/include/c++/backward",
                "C:/MinGW/lib/gcc/mingw32/6.3.0/include",
                "C:/MinGW/include",
                "C:/MinGW/lib/gcc/mingw32/6.3.0/include-fixed"
            ],
            "defines": [
                "_DEBUG",
                "__GNUC__=6",
                "__cdecl=__attribute__((__cdecl__))"
            ],
            "browse": {
                "path": [
                    "C:/MinGW/lib/gcc/mingw32/6.3.0/include",
                    "C:/MinGW/lib/gcc/mingw32/6.3.0/include-fixed",
                    "C:/MinGW/include/*",
                    "${workspaceRoot}"
                ],
                "limitSymbolsToIncludedHeaders": true,
                "databaseFilename": ""
            }
        }
    ]
}

You can automatically configure build tasks and start a debug session for your current C++ file using the 'Build and Debug Active File' feature. This feature automates the creation of configuration files and the execution of the build/debug cycle.

There are three ways to trigger this:

1. Command Palette: Open the command palette and select C/C++: Build and Debug Active File. This generates a tasks.json file, builds the active source file, and launches the debugger.
2. Context Menu: Right-click anywhere in the editor field while editing a file in your workspace and select Build and Debug Active File. This also generates a tasks.json file, builds the file, and launches the debugger.
3. Keyboard Shortcut: Press F5. This method is more comprehensive as it configures both a tasks.json and a launch.json file, builds the active source file, and then launches the debugger.

To debug MIEngine on Linux/macOS using MonoDevelop (Xamarin Studio):

Prerequisites:

• Install GTK.
• Install Xamarin Studio v5.10.1.6.

Setup:

1. Launch MonoDevelop with the remote attach flag:

   cd "\Program Files (x86)\MonoDevelop\bin"
   set MONODEVELOP_SDB_TEST=1
   MonoDevelop.exe

2. Create an empty 'Misc/Generic Project' in MonoDevelop to enable the Run menu.
3. In the project 'Options' -> 'Run' -> 'Custom Commands', set 'Execute' to a valid command (e.g., c:\windows\notepad.exe).
4. Enable remote debugging in the extension by opening ~/.vscode/extensions/ms-vscode.cpptools-<version>/debugAdapters/OpenDebugAD7 and uncommenting the line at the bottom.

Attaching:

1. In MonoDevelop, go to Run -> Run With -> Custom Command Mono Soft Debugger.
2. Enter the IP and port of the Linux/macOS machine and click Connect.