nils.hoelscher
/
RTSA-lab01-CacheAnalysis
1
1
Fork 1
Code Issues Pull Requests Releases Activity

Better Setup.

This commit is contained in:
Nils Hölscher 2022-04-20 10:15:56 +02:00
parent f25eba1687
commit 2a7d13c296
2 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
.vscode/tasks.json vendored Normal file
View File

@ -0,0 +1,13 @@
{
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "build",
"type": "shell",
"command": "cd build ; cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS=1 -DLT_LLVM_INSTALL_DIR=$LLVM_DIR ../CacheAnalysisPass/ ; ninja",
"group": "build"
},
]
}

8
README.md
View File

@ -31,16 +31,24 @@ For this setup you cannot use the OSS version of VS code or the version from Sna
2.) We recommend you install the following extensions in vs code 2.) We recommend you install the following extensions in vs code
clangd, clangd,
Clang-Format,
CodeLLDB, CodeLLDB,
Docker and Docker and
Remote Development Remote Development
For a general C/C++ setup of VS Code (I consider good) see:
<https://ahemery.dev/2020/08/24/c-cpp-vscode/>
Most of the setup can be skipped
3.) Use the helper script to build and run a Container 3.) Use the helper script to build and run a Container
./helper.sh docker ./helper.sh docker
This will build a docker image and run a Docker container with the current directory mounted. This will build a docker image and run a Docker container with the current directory mounted.
The Docker container can later be started from the Docker VS Code extension.
4.) Attach VS Code to the container, in the Docker Tab, and start developing 4.) Attach VS Code to the container, in the Docker Tab, and start developing
## Debugging ## Debugging