code-d transparently embeds DUB projects into the VSCode build tasks system.
To get a list of supported build and run operations for your project within VSCode click Terminal -> Run Task....
(1) A list of recently used tasks for repeated use.
(2) A full list of all detected DUB tasks for this project.
You can copy the tasks into the special .vscode/tasks.json file by pressing the cog icon on the detected tasks. To quickly launch one of the configured tasks, press Ctrl-Shift-B or Run Build Task in the command palette to immediately run the build task or select from your custom defined list of build tasks.
When you select a build task, for example "Run <project name>", it will pop up in the integrated command line in VSCode:
By default code-d passes all the currently configured build arguments to DUB. At the bottom bar it's possible to change all these arguments to manipulate build and plugin behavior. From left to right:
In here you can select the configuration of your application to run. You can manually define any configurations you want and they will replace the built-in ones by default.
DUB provides an application configuration and a library configuration by default:
-
the
applicationconfiguration includes all source files and runs your program as executable file. -
the
libraryconfiguration is nearly the same, except it will generate a statically linkable library for use in other applications. By default it also doesn't compile in the main source file (source/app.d)
The configurations application and library are usually automatically picked. When only running dub build or dub run it will always pick application if a main source file exists. Otherwise when no main source file exists, or when the project is used as a dependency in another project, it will use the library configuration.
See https://dub.pm/package-format-json.html#configurations
The architecture determines for which platform architecture the binary is going to be generated. Commonly these include:
-
x86for 32-bit apps on an Intel-based CPU -
x86_64for 64-bit apps on an Intel-based CPU
Depending on the selected compiler this might include more architectures for cross compiling.
You can select a build type out of a predefined list or anything else which is defined in the dub package file. The build types change how the compiler is invoked for building and are combinations of build options.
See https://dub.pm/package-format-json.html#build-types
To change which compiler is being used for running your program, you can click the compiler button. In here you can enter any compiler you want to use which you have locally installed.
Enter either a short name like ldc2, dmd or gdc in here if you have the compilers installed and available in your PATH.
If you only have portable installations of your compilers, enter a full path like C:\D\dmd2\windows\bin\dmd.exe in here.
It's possible to customize the default build tasks which you have available. Simply use the Configure Task command (or the siblings of it)
Then select the task you want your custom task to be based off:
A tasks.json file will be generated with the new task in there as placeholder.
You can use the built-in dub types to have a simple configuration for dub or you can also define custom shell commands which use the D problem matcher to show issues in code when running. You can check out the documentation by Microsoft on this.
Use the auto completion and validation to discover possible fields and values in the custom tasks.
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"type": "dub",
"run": false,
"problemMatcher": [
"$dmd"
],
"group": "build"
}
]
}Debugging your application