hledger/bin/compile.sh

#!/bin/sh
# Compile all add-on scripts in this directory.
# Keep synced: compile.sh, scripts*.test, hledger-*.hs ...

cd "$(dirname "$0")" || exit

echo "building hledger libraries for scripts"
stack build hledger

echo "installing extra libraries for scripts"
stack install string-qq

echo "compiling the hledger-* scripts"
for f in `git ls-files 'hledger-*.hs'`; do stack ghc -- "$f"; done
bin: add-ons compile script 2017-01-08 21:24:33 +03:00			`#!/bin/sh`
bin: switch to "runghc", drop "env -S" (#1453) env -S isn't a thing on linux of course. Go back to using standard env, which means using a stack options line, which means not using "ghc". This new setup is probably simpler anyway. I've just had to give up on the goal of having each script's required packages being defined in one place; now (to they extent they are required) they must be defined both in the script header and in compile.sh. 2021-01-12 21:55:00 +03:00			`# Compile all add-on scripts in this directory.`
;bin: linux/pr CI uses ghc 8.2, make functest uses default ghc (#1453) 2021-01-12 23:09:02 +03:00			`# Keep synced: compile.sh, scripts.test, hledger-.hs ...`
ci: also test compilation of bin/ add-on scripts 2020-12-28 23:44:53 +03:00
			`cd "$(dirname "$0")" \|\| exit`

bin: switch to "runghc", drop "env -S" (#1453) env -S isn't a thing on linux of course. Go back to using standard env, which means using a stack options line, which means not using "ghc". This new setup is probably simpler anyway. I've just had to give up on the goal of having each script's required packages being defined in one place; now (to they extent they are required) they must be defined both in the script header and in compile.sh. 2021-01-12 21:55:00 +03:00			`echo "building hledger libraries for scripts"`
bin: add-ons compile script 2017-01-08 21:24:33 +03:00			`stack build hledger`
ci: also test compilation of bin/ add-on scripts 2020-12-28 23:44:53 +03:00
bin: switch to "runghc", drop "env -S" (#1453) env -S isn't a thing on linux of course. Go back to using standard env, which means using a stack options line, which means not using "ghc". This new setup is probably simpler anyway. I've just had to give up on the goal of having each script's required packages being defined in one place; now (to they extent they are required) they must be defined both in the script header and in compile.sh. 2021-01-12 21:55:00 +03:00			`echo "installing extra libraries for scripts"`
ci: also test compilation of bin/ add-on scripts 2020-12-28 23:44:53 +03:00			`stack install string-qq`

bin: switch to "runghc", drop "env -S" (#1453) env -S isn't a thing on linux of course. Go back to using standard env, which means using a stack options line, which means not using "ghc". This new setup is probably simpler anyway. I've just had to give up on the goal of having each script's required packages being defined in one place; now (to they extent they are required) they must be defined both in the script header and in compile.sh. 2021-01-12 21:55:00 +03:00			`echo "compiling the hledger-* scripts"`
			for f in `git ls-files 'hledger-*.hs'`; do stack ghc -- "$f"; done