diff options
| author | Ben Sima <ben@bsima.me> | 2022-06-27 12:44:45 -0400 |
|---|---|---|
| committer | Ben Sima <ben@bsima.me> | 2022-07-05 19:03:06 -0400 |
| commit | ab2b9e4e3e9a433f75761314e54750f014c13b83 (patch) | |
| tree | 8e80134ce434f7331e75a0c135a51a7b68a8c8d2 /Biz | |
| parent | b72f6ba9f7a6987f184ac510491e452c3ea855b1 (diff) | |
Doc fixes
Diffstat (limited to 'Biz')
| -rw-r--r-- | Biz/Bild.hs | 9 |
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. |