Now, in order to set up the builder at a given remote @ commit , we
will want to make
${docker_src}/built/openwrt-builder-remote_commit.sentinel
... and then use the openwrt-builder-remote_commit image as a base.
New remotes can / should be added to openwrt-remotes.txt. Honestly
this oughta have been under the openwrt dir but, eh.
Now we can set up an OpenWrt builder as we want -- just run
make built/openwrt-builder-${commit}.sentinel
and then
docker run ${args} openwrt-builder-${commit} ${CMD}
This will won't need to pull down everything from scratch: the image
is already cached and has everything it needs to compile.
As for what ${args} would need to be for this to work:
- You need to mount a +x build system prep script to /input.sh
- You need to mount a +x build system output extractor to /output.sh
- You need to mount a folder with input resources to /input
- You need to mount an output folder to /output
So, /input.sh could `cp /input/diffconfig /builder/openwrt/.config`,
then cd to /builder/openwrt and run `make defconfig`. The ${CMD} could
then actually build, and /output.sh could collect logs and build
artefacts to /output.
But each of those build system setups can be disincluded from the
main build-system setup per-commit. We no longer have to repeatedly
setup the entire build system just to keep build environments for
different boards separate: only the things that are different between
build trees need that to be done.
Oh, and no more builds spoiled by stale artefacts :D
The point of this is to separate dockerfiles and build them on top of
each other wherever possible.
Then we can build them interdependently with makefiles!
