[hakyll] Re: Could not find module ‘Hakyll’

[h***@gmail.com]

I ran into this too, and was confused for a bit, probably because I haven't
been using stack for very long. The following worked for me:

hakyll-init .
stack init
stack build
stack exec site build

Based on my (admittedly limited) experience with stack, I'd much rather use
this setup than a cabal sandbox.

It might be nice to mention this approach in the documentation, maybe even
replace the current installation / basics tutorials? I'd say stack is much
more appropriate for new users. As far as I can tell, the current docs
assume hakyll is in your global package database, which is a recipe for
pain if you're using GHC for anything else at all on the same machine,
unfortunately. I'd happily send a PR addressing this if any maintainers
agree.

Harry

The problem is if you install hakyll with stack then the hakyll library is
not in the global packages. So when you run `ghc --make -threaded site.hs`
it complains that it could not find the Hakyll module.
`cabal sandbox init`
`cabal install --only-dependencies`
`cabal build`
then instead of `./site build` it becomes `./dist/build/site/site build`.
It might be worth it to put some kind of note about this issue when
installing hakyll with stack.

[Jasper Van der Jeugt]

I have no idea what's the distribution of how people install Hakyll. I
would assume a lot of people still have it in their global package
database or a cabal sandbox. To new users, I would also recommend
stack though, it seems less of a hassle.

Peace,
Jasper

Post by h***@gmail.com
I ran into this too, and was confused for a bit, probably because I haven't
hakyll-init .
stack init
stack build
stack exec site build
Based on my (admittedly limited) experience with stack, I'd much rather use
this setup than a cabal sandbox.
It might be nice to mention this approach in the documentation, maybe even
replace the current installation / basics tutorials? I'd say stack is much
more appropriate for new users. As far as I can tell, the current docs
assume hakyll is in your global package database, which is a recipe for pain
if you're using GHC for anything else at all on the same machine,
unfortunately. I'd happily send a PR addressing this if any maintainers
agree.
Harry

The problem is if you install hakyll with stack then the hakyll library is
not in the global packages. So when you run `ghc --make -threaded site.hs`
it complains that it could not find the Hakyll module.
`cabal sandbox init`
`cabal install --only-dependencies`
`cabal build`
then instead of `./site build` it becomes `./dist/build/site/site build`.
It might be worth it to put some kind of note about this issue when
installing hakyll with stack.

--
You received this message because you are subscribed to the Google Groups "hakyll" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/d/optout.