Nemea VS Code

This folder contains basic development environment for remove development using visual studio code. The virtual machine during provisioning clones nemea repository and compiles it for basic development.

Requirements

• Visual studio code from official microsoft repository. Otherwise the Remote - SSH plugin is unavailable from market place.
• Extensions for vscode are locateted inside virtual machine.
• Configuration and tasks for vscode are copied once at vagrant provisioning inside the cloned nemea repository inside the virtual machine.
• Working installation of vagrant

Instalation

    vagrant plugin install vagrant-sshfs
    vagrant up
    vagrant ssh-config

Copy the ssh settings inside you .sshd config. Inside vscode Ctrl+Shift+P Remote-SSH: Open Configuration File Replace the default name with appropriate name.

Local nemea repository

It is possible to clone nemea repository and retain it inside host system by cloning nemea repository to this folder under nemea-repo. git clone --recursive https://github.com/CESNET/nemea Afterwards the whole build and operation will be done inside this folder mounted by sshfs

Visual studio code connect

Inside vscode Ctrl+Shift+P Remote-SSH: Connect to Host Select from list the name of the ssh-config configured earlier.

After connected to the VM for the first time, you should see pop-up on the right side to install recommended extensions. These will allow IDE functionality for the cpp and autoconf project.

Visual studio code

The visual studio code project comes with prepared tasks for configuring and building the nemea project.

• Ctrl+P task bootstrap
• Ctrl+P task configure
• Ctrl+Shift+B or Ctrl+P task make
• Ctrl+P task test
• Ctrl+P task clean
• Ctrl+P task distclean

These task can be configured from repository files inside .vscode. There is also preconfigured cpp settings acording nemea C and C++ standards with enabled tracing for proper autocompletion using intercept-build generating compile-commands.json.

Troubleshooting

If you are expeiriencing failing intelisenes or syntax errors inside vscode make sure that the file is being processed by the build system.

Afterwards try reinstalling extensions inside the remote ssh machine. Extensions inside the VM are:

• maelvalais.autoconf
• ms-vscode.cpptools

Filesystem

The user is operating under vargant user with standard home /home/vagrant. The nemea repository is situated inside the /home/vagrant/nemea-repo.

Python development

Python libraries from pytrap, pycommon are installed in development mode inside the system.

CLion support

Unfortunatly i don't like CLion so i have not added support for JetbrainsIDE. The jetbrains remote development supports mainly cmake and i'm not sure if it can easily support autotools project. CLion remote development