5 Approaches to Remote C++ Development With CLion – Webinar Recording

The recording for our webinar, 5 Approaches to Remote C++ Development With CLion, with Matt Ellis and Timur Doumler, is now available for you to watch. Subscribe to our community newsletter to receive notifications about future webinars.

Webinar agenda

The webinar consists of the following parts:

  • 00:00 Introduction
  • 05:00 Remote development with Gateway
  • 20:45 Remote development with local sources
  • 32:00 Containers and virtual machines: WSL
  • 36:22 Containers and virtual machines: Docker
  • 43:29 Making Raspberry Pi blink an LED by debugging remotely from CLion
  • 56:11 Code With Me, collaborative editing (Matt now blinks an LED on Timur’s Raspberry Pi!)
  • 01:07:55 Recap of the options, comparison table
  • 01:11:36 Back to remote development with Gateway
  • 01:14:14 Q&A and wrap-up

Here are some related links and resources:

  • Remote development with Gateway:
  • A comparison of the other remote modes in addition to Gateway. Remote development with the thin client (a.k.a. Gateway) is a work in progress and not currently present in the comparison table.
  • Detailed web help for full remote mode.
  • Web help for developing on WSL in CLion.
  • A video guide to Windows toolchains in CLion, by Timur Doumler.
  • Docker:
    • Web help for using the Docker toolchain in CLion.
    • A video guide to the Docker toolchain in CLion, by Timur Doumler.

Notable Q&A

Remote development with the thin client

Does the thin client inherit all options, plugins, etc. that I might have set up in CLion?
The plugins currently don’t migrate, but your color scheme, appearance, and so on do.

If I have a Linux server with access to the Internet and SSH only, can I connect and install everything via Gateway without needing any extras?
Absolutely! Gateway manages everything for you. If you give it a plain Linux server, it will look at what’s installed there already. If you don’t have an IDE, then it will download and install one, and connect to it. Then you can proceed with developing.

What are the requirements for Gateway?
Gateway can run on Linux, Windows, or macOS. The remote machine should run Linux. Please refer to this web help topic for more details.

Code With Me

What do I need to start with a collaborative session? Should I just follow the link shared with me, and will it download everything?
From the guests perspective, the application will do everything for you. It will download the client and connect automatically. Learn how to get started as a host.

What is the licensing for Code With Me?
Code With Me is included in your IDE subscription. For example, if you own a CLion subscription, you can invite up to 50 guests who don’t have a subscription, and they will be able to follow you. Check out the Enterprise and other pricing options.

What about privacy for both Code With Me and Gateway?
All of the data is encrypted, so JetBrains can’t see anything. In the case of Code With Me, we try to do peer-to-peer. If that’s not possible, we have a relay server, where the data comes fully encrypted and is also secure. Please see this web help topic for more details on Code With Me security, and here you can find information about Gateway security.

Docker toolchain

Does a single build/run in a Docker container run stuff on a living container? Or does it spawn a container only for 1 run/build and then kills it after the build is finished?
Yes, it runs and kills it afterwards. But if the gap between the build and the run is less than 3 seconds, then the running container can be reused.

Can I specify the folder where I want to push code to Docker, and tell CLion to use an existing instance instead of rerunning the image?
No, the path is hardcoded. But you can use a generic remote host workflow for this scenario. The same advice applies to remote Docker containers, as the Docker toolchain in CLion currently only works with local containers.

Your CLion team
The Drive to Develop

image description

Discover more