invasy/remote-dev-gcc repository overview

⁠GCC in Docker

⁠Toolchain

⁠Usage

1. Build image:

   make gcc-build
   

   Copy
2. Run service:

   make gcc-up
   

   Copy
3. Set up CLion toolchain (see below).
4. Build, run, debug your project using toolchain in the container.
5. Stop service:

   make gcc-down
   

   Copy

⁠CLion Configuration

⁠Toolchains

• Name: remote-dev-gcc
• Credentials: see SSH Configurations below
• CMake: /usr/local/bin/cmake
• Make: /usr/local/bin/ninja (see also CMake below)
• C Compiler: /usr/local/bin/gcc (should be detected)
• C++ Compiler: /usr/local/bin/g++ (should be detected)
• Debugger: /usr/bin/gdb (should be detected)

⁠SSH Configurations

• Host: 127.0.0.1
• Port: 22002
• Authentication type: Password
• User name: builder
• Password: builder

⁠CMake

• Profiles:
  • Debug (or any other profile):
    • CMake options: -G Ninja

⁠SSH

⁠Configuration

# ~/.ssh/config
Host remote-dev-gcc
User builder
HostName 127.0.0.1
Port 22001
HostKeyAlias remote-dev-gcc
StrictHostKeyChecking no
NoHostAuthenticationForLocalhost yes
PreferredAuthentications password
PasswordAuthentication yes
PubkeyAuthentication no

Remove old host key from ~/.ssh/known_hosts after image rebuilding (note HostKeyAlias in config above):

ssh-keygen -f "$HOME/.ssh/known_hosts" -R 'remote-dev-gcc'

⁠Connection

ssh remote-dev-gcc

• User name: builder
• Password: builder

⁠See Also

• Remote development | CLion⁠
• Using Docker with CLion — The CLion Blog⁠