Developing on Linux (Arch) .. through OSX

As part of some development work on auto discover within a VMware environment (talked about here and here) I got quite fed up with having to move between Xcode for some code and vim/gcc in a linux VM or vSphere console. To try and streamline the work I decided to have a look at IDEs that are available for linux, excluding eclipse as it’s just too massive for the simple tasks I wanted..

223_linus_torvaldsSo I decided to have a look at Visual Studio Code and CodeBlocks as possible IDE solutions.

At which point the predicted vim abuse started on irc..

Names obscured and some text shortened.. (you get the idea)


09:13 <@A> a nice IDE for linux dev?
09:13 <@A> what's wrong with vim?
09:13 < B> lol
09:14 < dan> beard and sandals has arrived
09:14 <@A> newblets
09:14 < B> i can barely edit and save a text file in vim
[... first attempt with Visual Studio Code ...]
09:20 < dan> [dan@development ~]$ ./Code
09:20 < dan> ./Code: /usr/lib64/ version `GLIBCXX_3.4.14' not
found (required by ./Code)
09:20 < dan> f-ing linux
09:21 < dan> clearly ready for the desktop..
09:34 < C> :]
09:42 <@A> atom is an awful editor
09:42 <@A> and by awful i mean horrendously slow and bloated
09:44 < dan> :-)
09:45 <@A>
09:48 <@A> spoiler alert: it's not gotten any better

After a frustrating further 20 minutes I managed to get things working.. so here are my notes:

So I started with a base installation of Arch from their simple instructions and proceed to ensure that everything was up to date with a pacman -Syu.

I was wanting to access these linux IDEs through X11 forwarding from my desktop or macbook so the following packages are required (xeyes for testing and unzip for later):
pacman -S xorg-xhost xorg-xauth xeyes unzip
Along with the following changes to /etc/ssh/sshd_conf suggested from the Arch wiki, which was tested from mac to linux host with x11 forwarding on and starting xeyes. To resolve all of the dependancies for Visual Studio Code the following packages needed installing:

pacman -S gtk2 gconf nss alsa-lib libxtst

This will get you into a position where you’re ready to download and start Visual Studio code, however there are no fonts install on the system at this point so I opted for the Adobe source code fonts that are part of the Arch distribution:

pacman -S adobe-source-code-pro-fonts

After this it’s a case of heading to the Visual Studio Code download unzipping the archive and starting with./Code and this will present you with the fully working IDE:

VSCodeIt’s a nice IDE, however it’s clearly aimed at web and “cloud” applications for day to day use so I decided to try out the next best thing I could find, which was code blocks. This was a much simpler installation as it’s part of the Arch distribution and can be installed and ready to use with a much simpler:

pacman -S codeblocks

Which can then be easily started with the a simple codeblocks command presenting you with an IDE that is designed to actually work with compilers and linkers etc.. so in this instance i’m stuck with Codeblocks for the work i’m doing..


Leave a Reply

Your email address will not be published. Required fields are marked *