summaryrefslogtreecommitdiff
path: root/Biz
diff options
context:
space:
mode:
Diffstat (limited to 'Biz')
-rw-r--r--Biz/Bild.hs9
1 files changed, 4 insertions, 5 deletions
diff --git a/Biz/Bild.hs b/Biz/Bild.hs
index 43be7b0..4d55e0b 100644
--- a/Biz/Bild.hs
+++ b/Biz/Bild.hs
@@ -24,6 +24,9 @@
-- * never concerned with deployment/packaging - leave that to another tool
-- (scp? tar?)
--
+-- * local dev builds should be preserved, while remote nix builds are used
+-- for the final package
+--
-- == Features
--
-- * namespace maps to filesystem
@@ -64,10 +67,6 @@
-- This will build the file at ./A/B.hs, which translates to something like
-- `ghc --make A.B`.
--
--- > bild -p <target>
---
--- build target with profiling (if available)
---
-- == Build Metadata
--
-- Metadata is set in the comments with a special syntax. For system-level deps,
@@ -90,7 +89,7 @@
-- When multiple compilers are possible (e.g. ghc vs ghcjs) we use the @out@
-- extension, for example we chose ghcjs when the target @out@ ends in .js. If
-- @out@ does not have an extension, each build type falls back to a default,
--- usually an executable binary.
+-- namely an executable binary.
--
-- This method of setting metadata in the module comments works pretty well,
-- and really only needs to be done in the entrypoint module anyway.