Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>GEA Build ToolsNew to Visual Studio Code? Get it now.

GEA Build Tools

gea-embedded

|
78 installs
| (0) | Free
GEA build system integration for cpptools
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

GEA Build Tools

Generates VS Code configuration files for C/C++ projects using the GEA build system.

Configuration

First, run the Make Config File VS Code command (press ctrl/⌘ + shift + p) to generate a skeleton configuration in .vscode/gea_build_settings.json. This file should be committed to git. It will look something like this:

{
  "defaultDefines": {
    "RELEASE": "N",
    "DEBUG": "Y"
  },
  "configurations": [
    {
      "name": "target (Release)",
      "makefile": "target.mk",
      "defines": {
        "DEBUG": "N",
        "RELEASE": "Y"
      }
    }
  ],
  "version": 1
}

Makefiles and their associated settings using the GEA build system are listed under configurations. Each makefile will be used to (re-)generate configurations under .vscode/c_cpp_properties.json, .vscode/launch.json, and .vscode/tasks.json whenever a makefile changes. Since these files are machine-generated, it's best if these files are included in your .gitignore.

The name field is an optional field that allows you to override the name for the project as listed in the generated configuration. If name is not provided, the configuration name is taken from the makefile itself. This key is useful if you want to define separate release and debug configurations that need to have different names but are based on the same makefile.

The variables listed under defines are used when invoking the makefile to generate the configuration. Variables listed in defaultDefines are defined by default unless overridden by the defines for a specific target.

Including Non-Generated Configuration Items

Managed VS Code configuration files are removed before being generated. This means that any manually added contents will be removed. In order to include non-managed contents in the configuration files, you can create template files named .vscode/c_cpp_properties.gea-build-template.json, .vscode/launch.gea-build-template.json, or .vscode/tasks.gea-build-template.json. These templates will be used as the initial state of the corresponding VS Code configuration file before generation so they use the same schema as the corresponding configuration file.

  • Contact us
  • Jobs
  • Privacy
  • Terms of use
  • Trademarks
© 2023 Microsoft