Reflex-platform: a more complex packaging use-case

[Kostiantyn Rybnikov]

Hi!

I am starting to use reflex as an addition to our projects, there's a somewhat sophisticated way to build our project using stack, which involves things like:

- building local packages (our own and forks we're using)

- building some projects from github commits

While I succeeded using stack to build reflex-based project, I'd like to also try reflex-platform way, since it seems to be providing ghci repl on linux (if I understood correctly).

What's the best thing to do? Should I just dig into ./try-reflex sources and Nix packaging system, or are there some shortcuts to achieve what I need? Thank you!

[Sean Leather]

Hi Kostiantyn,

I assume you're mostly talking about installing GHCJS.

I can't help you with the reflex-platform approach to building. I've used Nix to install GHCJS, but, unless you're already using NixOS, I wouldn't recommend it due to the massive number things that need installing and building.

Personally, I've found it more useful to use Stack to build GHCJS. I discovered recently that this can even be done without a stack.yaml:

> stack setup ghcjs-0.2.0_ghc-7.10.2

Regards,

Sean

[Kostiantyn Rybnikov]

Hi Sean,

Stack already works quite well, I just thought nix-based setup build could bring some benefits like having "ghcjs --interactive" support on linux, but after searching a bit the only mention I've found was regarding try-stack-reflex actually [0] which has something similar. Another potential benefit I see is that it's possible that it's easier to use manually-built ghcjs and its libraries with nix-based approach, but maybe that's not the case as well, need to figure out.

Anyway, I will probably leave nix-based approach for now, but things mentioned in original post would still be nice to have there, as reflex-platform tries to bring stack-like instruments to cover haskell development for reflex-based apps.

[0]: https://github.com/luigy/try-stack-reflex