Closed rosenk closed 8 years ago
Here's a workaround: you don't have to compile on the Pi. Compile your Elm to JS on a "real computer", and then copy the JS to the Pi.
ARM computers are real computers. :stuck_out_tongue: But +1 from me anyway.
@mgold Re the JS files, which ones are to be copied? So far I have
# find / -name "elm" 2>/dev/null
/usr/lib/node_modules/elm
/usr/lib/node_modules/elm/Elm-Platform/0.16.0/.cabal-sandbox/bin/elm
/usr/lib/node_modules/elm/binwrappers/elm
/usr/bin/elm
/root/.npm/registry.npmjs.org/elm
/root/.npm/elm
Not Elm itself, but the result of compiling an Elm program. By default this is index.html
but can be changed with --output
. If you supply a filename ending in .js
the compiler will output only JS and not HTML.
Ah I see - thanks - out of necessity I've been using that method in my workflow.
I can't commit to supporting ARM builds on my own. I know @rtfeldman has done work on automating the creation of binaries, so if we can figure out how to make ARM versions, that'd be great!
I don't think keeping this issue open will make that outcome more or less likely, so I am going to close.
+1 on this if it makes any sense for such a comment.
Too bad that Elm can not be used on a Raspberry Pi :-(
Sharing @daniel-kun 's Raspberry Pi solution... https://dev.to/danielkun/using-elm-on-a-raspberry-pi-42pi
Thanks @gabethexton for supporting this issue. By the way, I also compiled Elm on a 96 core Arm v8 (dual socket Cavium ThunderX SoC) from packet.net, which was NOT faster than bulding it on a raspi, because the builds of GHC, Cabal and maybe Elm itself (I can't remember exactly anymore), were not parallelized. Quite a pity... I hoped to see those 96 cores doing some heavy lifting :-)
On Raspberry Pi 2:
npm -g install elm
Unfortunately, there are currently no Elm Platform binaries available for your operating system and architecture.
Building from source is a horrific experience on such slow device. I tried but ghc is running out of ram or something.