| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
The conversion was made so that the build command was used instead of
the build-morphology command.
Change-Id: I67c43d765ed603ecdd806bc649815526243b7b87
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of logging every command for ourselves, use the shell X-ray
mode. As side effect, each command argument will now be printed out in
its evaluated form, which aids debugging.
Also, improve the visual separation between the different build steps,
and display those steps with finer granularity.
Change-Id: I16ebe9ba4ac46fef82e37d0b3e05f42d14249de8
|
|
|
|
|
|
|
|
|
| |
When I spotted that artifacts contained a .git directory I was worried
that it might indicate a Morph bug. It turned out to be due to the way
the 'test shell' used in the Yarn tests works. This change should save
anyone else from similar confusion.
Change-Id: I97b57eff7aa947506d4062a76e9803398e46c2b6
|
|
|
|
| |
Change-Id: I46ad9c15064de752e839611d2ce3ee016ec7cc46
|
| |
|
|\
| |
| |
| |
| |
| | |
Reviewed-by: Sam Thursfield
Reviewed-by: Pedro Alvarez
Reviewed-by: Daniel Silverstone
|
| |
| |
| |
| |
| |
| | |
It now works when passed a file, rather than a command to run, and
ignores comments and set commands, so the generated preamble is
accepted.
|
|/ |
|
| |
|
|
This is intended to be statically linked, so it can be run in the
staging area, without having to build a libc.
You shouldn't generally statically link GLibc, because it dynamically
links things like NSS modules or locale data, but we only need some very
simple stuff, so we can get away with that.
There's also potential licensing issues, as GLibc is LGPLv2, so
distribution requires providing the ability to re-link against another
library, but its use in the test-suite shouldn't count as distribution.
There's a couple of commands, the only two needed by the yarn test
suite are "copy files" which is like `cp -r . "$DESTDIR"`, and "false",
which is for commands to deliberately fail.
|