| #
ae0a10ca |
| 16-May-2021 |
Adrien Destugues <pulkomandy@pulkomandy.tk> |
Update readme for docker images
There was some confusion about what they are and how they are used.
Hopefully this clarifies things a bit.
|
| #
5c9ee5d0 |
| 09-Dec-2019 |
Alexander von Gluck IV <kallisti5@unixzen.com> |
docker/bootstrap: rename init to prep to be consistent
Change-Id: Ie6dc9061b13b23997f84a1ffe886d7e09c242cf0
|
| #
54624bda |
| 15-Feb-2019 |
Alexander von Gluck IV <kallisti5@unixzen.com> |
bootstrap: Add some tools to test bootstrap steps
Change-Id: Idac85d5b7c1fadd371efd13fa788a03656e82e66
|
| #
3a922841 |
| 04-Nov-2018 |
Alexander von Gluck IV <kallisti5@unixzen.com> |
docker/bootstrap: Make README.md a bit more detailed
Change-Id: If095b584cd99521770280533359da5024ff745bf
|
| #
131f0990 |
| 02-Nov-2018 |
Alexander von Gluck IV <kallisti5@unixzen.com> |
docker/bootstrap: Add a few tools to bootstrap in a container
* The bootstrap process will pick up on local toolchains such
as clang and use them instead of the correct gcc cross-tools.
* This lim
docker/bootstrap: Add a few tools to bootstrap in a container
* The bootstrap process will pick up on local toolchains such
as clang and use them instead of the correct gcc cross-tools.
* This limits environmental factors which can break bootstrap.
Change-Id: Iacdd2a44cf26e18f838c9251fb9eddfbcb12565e
show more ...
|