Add support for small(er) Docker images to use (not work on) Lucet#201
Add support for small(er) Docker images to use (not work on) Lucet#201
Conversation
|
I like this, but it doesn't look like it gets used from CI at all, so we'd be depending on user reports if it bit rots and breaks. Is there a sensible way to test it with travis? |
|
I can add this to Travis, but as this is going to make the builds take more time to complete, we will get closer to the point where Travis will explode. But let's try :) |
|
Ok. If this is the straw that breaks Travis's back, we can merge it without CI. Thanks for giving it a try. Hopefully we wont be on Travis for too much longer. |
Building the toolchain in release mode is too slow for CI. So, introduce an `install-dev` target, that reuses the debug build. The overhead is reasonable.
jedisct1
force-pushed
the
fdenis/lucet-toolchain
branch
from
222815c to
b497e62
Compare
|
Some changes have been added to the Travis builds. We now build the Just like in non-CI mode, except that what gets installed is the binaries compiled in debug mode. When the same scripts are run outside CI, they are still compiled in release mode. |
2 participants
This adds the ability to build a new Docker image,
lucet-toolchain, that only contains the Lucet toolchain, and not the boilerplate to build it.Lucet tools can then be directly used as:
This image is based on the current Ubuntu, and uses the stock LLVM installation, so it can be used as a base image for projects willing to build upon Lucet.