It finally happened! They did it! They did it just in time for me to get on the road and start building applications on the road with my shiny new laptop, too! JOY!! Oracle and the GraalVM team released GraalVM and the GraalVM native image capability for Apple M1! I’ve been waiting for this day for so, so, so long! I bought the first Apple M1 the day of the announcement way back in 2020 (does anybody remember that far back? That was, meteorologically speaking, the early pandemic period).
Apple’s M1 devices are insanely fast, energy-efficient beasts of machines that run circles around all but the beefiest and latest-and-greatest Intel/NVidia configurations while also consuming a pittance of the power that other configuration does. In short, I’m a big fan. But the move to this new architecture hasn’t been without its troubles.
Some Adobe applications (like Adobe Premiere and Adobe After Effects), Docker, and GraalVM were the biggest hurdles to making my M1 machine (which I have since upgraded from the first 13" MacBook Pro 2020 M1 to the 16" MacBook Pro 2021 M1 Max model) my daily-driver. Docker’s gotten better. Adobe Premiere’s gotten better, and After Effects isn’t too far behind (but still no joy there). And now, as of yesterday, at long last, GraalVM has gotten better.
However, it’s not yet GA, and it’s not even in the fantastic SDKman project. So installing it could’ve been tedious. Do you all remember adding things to your
PATH manually? I do, and I don’t like it! So I Googled but came up empty. Then, just when I’d resigned myself to having to work , I realized my incredible friend and community legend Matt Raible (@mraible) had already figured it out. So I pinged him, and he sent me this ticket he’d filed against the M1 build and Spring Native detailing how he got it working and how to verify the break.
Here are his steps as they applied to me. NB: I think they’ve since released a newer version of GraalVM even since one day ago when Matt wrote the blog, so as a result, my version numbers are
.1 off from his.
I put that
.tgz file on my
$HOME/Desktop and then ran this script to get it installed and usable for
SDKMan . These are the same steps as Matt details in his original ticket.
Put all of those instructions in a text file called
install.sh on your
$HOME/Desktop , then run
chmod a+x $HOME/Desktop/install.sh to make it executable and then run it with
Youll need to make this newly installed version the default one for your operating system, so issue the following command:
Once that’s done, you’ll need to install the
native-image compiler command with the
gu utility in the GraalVM distribution:
Open a new shell and verify that everything’s working:
With that, you should be all set. Then you need an application against which to test. So go to my second favorite place on the internet, start dot spring dot io, and generate a new application with everything pre-configured. Click
Generate and then unzip and open the resulting
pom.xml in your Java IDE of choice.
M1NativeApplication.java with the following contents:
There ya go: you have a reactive, non-blocking web application talking to an embedded, in-memory SQL database. Let’s turn this thing into a native image. On the command line, run the following incantation:
That’ll take about 45 seconds to finish. Have a few sips of coffee and then run the application in your target/ directory:
Hell yeah! Rock on GraalVM! This is amazing! I know there are bound to be bugs or issues, but the fact that this works so well for nothing but a developer preview build? That’s dope.
Now to figure out what to do with my creakingly old and irrelevant Intel MacBook Pro…