Is it possible to set environment variables? #22
Comments
This was referenced Jul 15, 2015
evancz
pushed a commit
to elm-lang/elm-reactor
that referenced
this issue
Aug 13, 2015
This change starts using Template Haskell (TH) to bundle the necessary compiled Elm code in the binary. This will mean we no longer need an ELM_HOME and can avoid kevva/elm-bin#22 entirely. This also introduces the cabal-build.py build script which touches the TH file if any of the Elm resources have been modified since lasts we compiled. It also cleans up the new index code a decent amount. We took out all the icons in favor of font-awesome which can again be bundled with the binary instead of living in ELM_HOME.
|
This has been messing things for a lot of folks, so as we were doing some recent work on Elm Reactor, I decided to bundle the static resources in the binary itself so that no one needs ELM_HOME anymore. That should be out with the next release of the platform. The root problem here is still pretty bad. We hear about this on the mailing list and various repos pretty often. |
|
This is done now on the elm-platform npm installer, and can be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
elm-reactor needs ELM_HOME, is that resolved? Can you point me to the relevant code if so?
We do different tricks with the mac and windows installers to do this. On mac we turn elm-reactor into a two part binary. The public one
elm-reactoris just a thin wrapper that sets ELM_HOME to /usr/local/share/elm/ for the duration of the script and then callselm-reactor-unwrappedwhich is the actual executable. This avoids any issues around "this shell sets variables like this, but that shell sets variables another way". Would that work here?The text was updated successfully, but these errors were encountered: