From 87b48d473bdb41670c9f3b26a628f34c3c5c9481 Mon Sep 17 00:00:00 2001
From: Ben Sima <ben@bsima.me>
Date: Fri, 3 Apr 2020 13:20:29 -0700
Subject: Rewrite buildGhc and buildGhcjs
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

I wanted to even further simplify the build tooling overhead. My general
goal is to not have to think about declaring packages, or dependencies,
or really anything that you might find in a cabal file. Not all of these
goals are possible, but we can get pretty close. With this commit all I
need for the 'buildGhc/buildGhcjs' functions is the path to the
entrypoint file; everything else is either inferred by the Nix code or
declared in the Haskell code comments.

The strategy is to map a Haskell module to an executable artifact, and
pass just that module to 'ghc --make'. Then we can rely on ghc to handle
walking the local filesystem for imports. The only thing ghc really
needs to know is a name for the output executable; it is hard to
automatically infer this, so we have a simple comment syntax to declare
this in the file. The comment syntax is inspired by existing Haskell
'LANGUAGE' pragmas; having this in the same file keeps the configuration
as close to the real code as possible. The Nix code then extracts this
info from the code comments, and sets the required ghc flags.

Second, we need to declare the set of 3rd-party packages that our
program relies on. For this we can re-use the same comment syntax and
just list the dependencies, then extract them in Nix and construct a
package set as we were before.

This reduces the amount of "package declaration" code we have to write
in default.nix, and reduces the amount of time we have to spend
switching between the Haskell code and the Nix code (I find such context
switching super annoying). I also think having the configuration in with
the Haskell code encourages us to write smaller, simpler modules and
only write code that we need.

Additionally, I refactored the bild and ghci (now called 'repl') scripts
to work in any directory. The .envrc uses direnv to set the path so that
you can run these scripts anywhere. That means the following works:

    $ cd Run/Que
    $ bild Website
    $ repl Server
    λ> :l Run.Que.Server

I find this to be a rather nice workflow.
---
 bild | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

(limited to 'bild')

diff --git a/bild b/bild
index 5b74ffb..8ea07ea 100755
--- a/bild
+++ b/bild
@@ -1,8 +1,11 @@
 #!/usr/bin/env bash
-nix build -o "_bild/$@" -f default.nix "$@"
-if [[ $? != 0 ]]
+set -ex
+prefix=$(echo $PWD | sed -e "s|^$BIZ_ROOT/*||g" -e "s|/|.|g")
+if [[ "$prefix" == "" ]]
 then
-  echo ":: bild fail"
-  echo ":: replaying the log..."
-  PAGER=cat nix log -f default.nix "$@"
+  target="$1"
+else
+  target="$prefix.$1"
 fi
+nix build -o "$BIZ_ROOT/_bild/$target" \
+  -f $BIZ_ROOT/default.nix "$target" --show-trace
-- 
cgit v1.2.3