On Fri, Sep 16, 2016, at 06:08 PM, Herbert Valerio Riedel wrote:
> Hi!
>
> On 2016-09-16 at 14:34:14 +0200, Ramakrishnan Muthukrishnan wrote:
> [..]
>
> > I will try building and trying the `master' branch. Thanks again.
>
> That's generally recommended with new-build at this point, since a lot
On Fri, Sep 16, 2016, at 06:08 PM, Herbert Valerio Riedel wrote:
> Hi!
>
> On 2016-09-16 at 14:34:14 +0200, Ramakrishnan Muthukrishnan wrote:
> [..]
>
> > I will try building and trying the `master' branch. Thanks again.
>
> That's generally recommended with new-build at this point, since a lot
Hi!
On 2016-09-16 at 14:34:14 +0200, Ramakrishnan Muthukrishnan wrote:
[..]
> I will try building and trying the `master' branch. Thanks again.
That's generally recommended with new-build at this point, since a lot
of things have improved in cabal 1.25/master since cabal 1.24;
Also, I'd also
Hi Lennart,
Thanks for the email. Sorry, I wrongly wrote the path "dist" when I
meant "dist-newstyle". When I created a fresh project, just doing `cabal
new-build' created a binary. Here is what I get in my blog directory.
ram@knuth:~/src/newblog$ cabal new-configure
Resolving dependencies...
In
The build artefacts of new-* are placed in a "dist-newstyle" directory.
Another common mistake with 1.24.0.0 is that `cabal new-build` won't
do much at all if run in some parent directory. You might need to
`cabal new-build ./my-blog/` and then get the artefacts somewhere
(burried) in
I have a fairly simple hakyll based blog website that I usually build
with cabal sandbox.
Today I tried the new-configure/new-build commands. It built a bunch of
dependencies but the dist/build directory is empty. It doesn't look like
it built the project itself. Subsequent builds are fast as
