Plugin support

[Perry Wagle]

Gitit is a wiki written in GHC/Haskell.  It supports plugins.  To do this is provides a library of modules that the plugins then import.

But, the "exposed-modules" are hidden away in a obscure directory, where they can't be found.

What's the correct solution?

Thanks!

-- Perry

[Michael Snoyman]

I can't speak for others, but from this email I don't understand what the question is. I'm personally not familiar with the plugin mechanism provided by Gitit. Perhaps you can provide a little more detail?

--
You received this message because you are subscribed to the Google Groups "haskell-stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to haskell-stack+unsubscribe@googlegroups.com.
To post to this group, send email to haskel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/f8c0922c-803a-45fc-a129-d1e4211c5f04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Perry Wagle]

I don’t understand its plugin mechanism either (yet),  but it seems to involve the GHC API for loading Haskell (compiled on the fly) modules at run-time, and running them.

The problem is that the linker isn’t told where the heck you squirreled away gait’s modules, so can’t link to them.

I don’t understand either gitit’s source code or stack’s philosophy/intent, so have no idea what the correct solution is.

— Perry

[Michael Snoyman]

If the question is "where is Stack placing compiled libraries," you can get that information by looking at the `stack path` output. In particular, the `stack path --snapshot-install-root` command may help.