... | ... | @@ -43,7 +43,7 @@ The VsCode has a built-in solution to manage project-related shell scripts. They |
|
|
{
|
|
|
"label": "make",
|
|
|
"type": "shell",
|
|
|
"command": "make -j10 -e CXXFLAGS=\"-g -O0\"",
|
|
|
"command": "command": "make -j10 -e CXXFLAGS=\"-g -O0\" && find ~+ -type d -name .libs | tr '\n' ':' | awk '{print \"LD_LIBRARY_PATH=\"$0}'> ${workspaceFolder}/.vscode/.env",
|
|
|
"dependsOn": "create envfile"
|
|
|
},
|
|
|
{
|
... | ... | @@ -56,12 +56,11 @@ The VsCode has a built-in solution to manage project-related shell scripts. They |
|
|
}
|
|
|
```
|
|
|
|
|
|
There are four tasks:
|
|
|
There are three tasks:
|
|
|
|
|
|
- `autoreconf` - call the autoreconf utility in the standard way. It should be called once after cloning the repository.
|
|
|
- `configure` - run the configure tool with the Google Test flag
|
|
|
- `make` - run the compilation with disabled optimizations to improve the debugging experience
|
|
|
- `create envfile` - run automatically before the `make` command. The VsCode C++ extensions very dislike `libtool` wrappers. The best workaround I found is to avoid using these wrappers and directly call the executables. But it requires setting the `LD_LIBRARY_PATH` environment variable. This script searches the proper paths and puts them into envfile. This file is further used in the configurations.
|
|
|
- `make` - first, run the compilation with disabled optimizations to improve the debugging experience and next it prepares the envfile. The VsCode C++ extensions very dislike `libtool` wrappers. The best workaround I found is to avoid using these wrappers and directly call the executables. But it requires setting the `LD_LIBRARY_PATH` environment variable. This script searches the proper paths and puts them into envfile. This file is further used in the configurations.
|
|
|
|
|
|
You can run the task by pressing `Ctrl + Shift + P` and typing `Tasks: Run Task`.
|
|
|
|
... | ... | |