diff options
| author | Richard Maw <richard.maw@codethink.co.uk> | 2014-10-02 11:14:49 +0000 |
|---|---|---|
| committer | Richard Maw <richard.maw@codethink.co.uk> | 2014-10-02 13:09:32 +0000 |
| commit | 9238bb78c8ab1e9d4dcb09298b32f66fdf0fd744 (patch) | |
| tree | 0da2c6c8a6fcb8da629a17d1fcfca4125ab2d80b | |
| parent | 72af290f4090809b8d11ae897670341621c96206 (diff) | |
| download | morph-9238bb78c8ab1e9d4dcb09298b32f66fdf0fd744.tar.gz | |
Test that morph can handle binary garbage output in builds
| -rw-r--r-- | yarns/implementations.yarn | 12 |
1 files changed, 11 insertions, 1 deletions
diff --git a/yarns/implementations.yarn b/yarns/implementations.yarn index 71b8af60..0c0daf79 100644 --- a/yarns/implementations.yarn +++ b/yarns/implementations.yarn @@ -282,12 +282,22 @@ another to hold a chunk. name: test-chunk kind: chunk build-system: manual - # `install-commands` is a list of shell commands to run. Commands + # `build-commands` is a list of shell commands to run. Commands # may be on multiple lines, and indeed anything programmatic will # benefit from doing so. Arguably we could have just one command, # but it's split into multiple so that morph can inform us which # command failed without us having to include a lot of status # information in the command and look at the error message. + # `build-commands` are passed MAKEFLAGS to specify build parallelism, + # and are expected to generate files to be installed in `install-files` + build-commands: + # All of morph's building needs to handle binary output, so we can echo + # that out on the command line. + # Trust me, this gets decoded to "echo " then a bunch of binary output. + - !!binary | + ZWNobyBQ1+k661ol3khrsF4VO4HNcuYzwN0LYxEWS8mPmhQiQ7Vu8CME2+gsnKQaoIRIFuUEiLCI + vfIj1GTdXG6cVTJfNQ== + install-commands: - copy files EOF |