Skip to main content

Add pre-compiled Elixir on OS X

So, I've been a big Erlang fan for a few years now, and then found out about Elixir:  what I would describe as kind of a Ruby-ish creamy frosting on top of Erlang. But I'll address more on both in future. Right now, I thought I'd just give a quick and dirty way to add Elixir, if you've already got Erlang installed (hint: check-out this Erlang Solutions link for a pre-compiled Erlang solution).  You can also use brew to install both, but I have found that with the simplicity of brew, you give up having the most current version of software.  In both cases. The pre-compiled zip for the most current version of Elixir can be found here.  Unzipping reveals a folder containing everything you need.  For simplicity's sake, keeping everything pertaining to Elixir all within this folder makes the most sense.  By doing so, all that's needed is to position the folder, and then make links to all the executables in a directory already in our path.  Through the link, the OS will find the program, and everything the program needs (libs and such) are already where it expects to find them (in the folder). Rename the folder to: "Elixir".  The reason I do this is so that I can easily find it later, and just drag the old folder to the trash, replacing it with whatever the current version is (and not have to change any of the links-- drag and drop replacement).
NOTE:  the following assumes that you have "/usr/local/bin" on your path.
Now, move (mv) the newly renamed folder to the directory: "/usr/local/", so that the final directory path is now, "/usr/local/Elixir". Again from the terminal, change directories (cd) to "/usr/local/bin", as it's from here that we're going to set every thing up to play nice. With the current directory in the terminal now, "/usr/local/bin" add the following soft links to each of the Elixir executables (beginning '$' represents the terminal prompt in all examples): 

$ ln -s /usr/local/bin/iex  iex

$ ln -s /usr/local/bin/elixir  elixir

$ ln -s /usr/local/bin/elixirc  elixirc

$ ln -s /usr/local/bin/mix  mix
Now, you can double check everything: 

$ iex -v
$ elixir -v
$ elixir -v
$ mix -v
Provided everything is set up correctly, and you received version number's from each command, you're ready to rock with Elixir.
Labels:
Location: Portland, OR, USA

Comments

Post a Comment

Popular posts from this blog

Java application opening then immediately closing on OSX

I have had several occasion's where Java apps would open, and then immediately close.  Often, I don't have the time to dig into the reason, as they aren't crucial.  So, I just move on. Recently, I was maddened by this happening to an application ( see other blog post on Kindle Previewer ) I really needed to use, so I had to get into the trench.  After cracking open the app, and rooting through the various files, I did some spot-checks of the java version used to build the jars ( 2 bytes at offsets 6 & 7 ), as well as had a look at the info.plist, which had the JVMVersion key set at 1.5+. Since Oracle took over Java, Apple has essentially abandoned it to them, and hasn't done an update I *think* since version 6. All of Apple's Tooling for Java stops with JVMVersion key's of 6* and 6+.  The short answer to all this is, if something was built using Apple's AppBundler tools, and you have updated Java on your Mac to 7 or above, you're probably SOL to g...
Post a Comment
Read more

Codeigniter vs. Kohana Database access speeds

I was doing some basic profiling for a project in which I needed the fastest raw speed I could get with database queries. I'm a fan of Codeigniter for projects that are suitable for it, but had heard from some that Kohana was faster, so I decided to do a very basic comparison of the two. I was using MAMP for OSX, and created a very small db, with a table that had 3 fields: (id), (first), and (last). The data sample was also very small, only a few records. The basic query I tested was a "SELECT * FROM [table]". There is of course nothing remotely scientific about this. It was just a quick ad dirty, very limited comparison. Take it as such. Versions used: CI2.1.3, Kohana 3.3.0. Codeigniter I really like Codeigniter (CI). But, one thing that is very evident from their own profiling functions, is that CI is a bit of a memory hog! Essentially, the same Controller function running in CI takes approximately 10X more memory than in Kohana! This in itself is not ...
Post a Comment
Read more