Make sure you can log in to the remote host without entering a password by copying the public part of your SSH-key to the remote host: ssh-copy-id remote-host.ĭouble-check that you can now log in using ssh remote-host. Replace the obvious bits in that definition. User USER_NAME_WITH_WHICH_YOU_LOGIN_TO_YOUR_REMOTE_HOST If you want to follow the tutorial step by step, you can put the following into your ~/.ssh/config file to create an alias to whatever host you want: For the sake of this tutorial, we’ll call the remote host just remote-host. My base system is a laptop running the Fedora 32 operating system. This article navigates you through how I’ve been using VS Code's remote SSH extension for editing and compiling LLVM, step by step. After giving Vim and Emacs another shot for coding and compiling remotely, I went back to VS Code and found out that there’s a remote SSH extension. Qt Creator wasn’t a true option for editing files remotely because, as far as I know, it needed to run next to the code it was supposed to compile. I live in Germany, and at first I was skeptical whether I could successfully use those machines without too much latency. Our group in Red Hat has access to high-powered shared machines in Toronto (e.g., 56 cores with 256 GB of memory). That said, distributed compilation using distcc or similar tools doesn't cut it. It’s the linking, as well, that can easily freeze my laptop. The speed of compilation isn’t the only thing that matters. To sum things up: A notebook isn’t ideal when you want to code and compile with LLVM. You can read about my initial endeavor to speed up the compilation in this article. I began by checking out the LLVM codebase-which is huge, by the way-and compiling it on my local machine, which was very slow. LLVM also hosts Clang, a well-known compiler front-end for C-like languages. Three years later, in 2019, I needed a change and joined our debuggers group to work on LLDB, a debugger that is part of the much larger LLVM project. But being new to Go, I figured I would give it a try, especially because others were using it. I can't say that VS Code worked out of the box. As usual for a modern project, I needed to be able to do more than edit the files of one programming realm. I gave Vim a shot when really I was looking for something that works out of the box and can still be customized. I’m a regular Vim user, but use it only for plain-text editing and not much more. I quickly realized that I wanted something similar to Qt Creator. Then I joined Red Hat around mid-2016 and worked on a project with Go for three years. I used the Qt Creator IDE for most of my C++ work in the past.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |