... | ... | @@ -7,6 +7,20 @@ Some remarks on how to configure the IDE to pleasant work with Kea. |
|
|
The [Visual Studio Code](https://code.visualstudio.com) is a popular IDE with built-in syntax checkers, debugging, and extensions support.
|
|
|
The vscode can easily handle the Kea repository, but the full integration is more challenging.
|
|
|
|
|
|
### tl;dr
|
|
|
|
|
|
1. Install all recommended extensions
|
|
|
2. Put these files in `.vscode` directory:
|
|
|
1. [settings.json](uploads/8cbd4a9e6861d77c58c768906963bbc8/settings.json)
|
|
|
2. [launch.json](uploads/6a9807e04a88d3799f39c41f2b23b722/launch.json)
|
|
|
3. [tasks.json](uploads/833679a1f066948fc7bd59ab95aa5460/tasks.json)
|
|
|
3. Run these tasks by pressing `Ctrl+Shift+P` and selecting `Tasks: Run Task`:
|
|
|
1. `autoreconf`
|
|
|
2. `configure`
|
|
|
3. `make`
|
|
|
4. Reload the unit tests by pressing `Ctrl + Shift + P` and selecting `Test: Reload tests by C++ TestMate`
|
|
|
5. Use the `Run and Debug` (icon with triangle and bug) or `Test Explorer` (icon with measuring cup) from the left sidebar to run a specific application or test.
|
|
|
|
|
|
### Recommended extensions
|
|
|
|
|
|
- Autoconf (maelvalais.autoconf)
|
... | ... | @@ -60,7 +74,7 @@ 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` - 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.
|
|
|
- `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`.
|
|
|
|
... | ... | |