... | ... | @@ -5,12 +5,13 @@ |
|
|
* Launch VSCode
|
|
|
* Open the folder containing the code
|
|
|
* CPP or Python (use Ctrl+X Ctrl+F)
|
|
|
* Take a look and edit ``.devcontainer/Dockerfile``
|
|
|
* Change **USER_UID** and **USER_GID** values if not set to *1000*. Use `id -u` and `id -g` to get your current ones.
|
|
|
* Take a look and edit ``.devcontainer/devcontainer.json``
|
|
|
* Change **USER_UID** and **USER_GID** values if not set to *1000* : use `getenv passwd yourlogin | cut -d: -f3-4`
|
|
|
* Click on the cogwheel icon in the bottom-left corner and select "Command Palette..." (or menu "View->Command Palette..."), then type "remote-container reopen"
|
|
|
* Click on the cogwheel icon in the bottom-left corner and select "Command Palette..." (or menu "View->Command Palette..."), then type "remote-container reopen in container"
|
|
|
* This will reload the VS Code window and wait for the container to come up
|
|
|
* This operation takes some time: an image will be built by VS Code according to ``.devcontainer/Dockerfile``, then a VS Code server will be installed automatically
|
|
|
* You can ignore the configuration messages
|
|
|
* This operation takes some time: an image will be built by VS Code according to ``.devcontainer/Dockerfile``, then a VS Code server will be installed automatically in the container instance
|
|
|
* You can ignore the configuration messages of CMake
|
|
|
* If you opened the C++ version: run the command *CMake: Debug target*
|
|
|
* When asked, choose GCC 6.3.0
|
|
|
* If you get the "Cannot connect to diplay" error, edit the ``.devcontainer/devcontainer.json`` file to setup the DISPLAY environment variable properly, then run the command *Rebuild container* |
|
|
\ No newline at end of file |