Make bootstrap tools an opt-in option when making chroot env. #125
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change replaces the
metal
Makefile targets withchroot
. Thatis,
make metal
,make metal-shell
andmake metal-destroy
have beenreplaced by
make chroot
,make chroot-shell
andmake chroot-destroy
respectively.
This change also alters the behavior of creating the chroot environments
for Docker containers, virtual machines, and bare metal. Now, the
tarballs required to populate the
/tools
directory are not addedto the chroot, leaving a pristine environment with no foreign software.
Until the basic build toolchain is complete (i.e. all software that is
being used in
/tools
), this directory is still required and can beused by adding
use_bootstrap_tools=true
environment varible to thevarious
make
commands:make image use_bootstrap_tools=true
make vm use_bootstrap_tools=true
make chroot use_bootstrap_tools=true