commit | f88a1c6cebeb7857c36d40b57d4ccc486a83dd1e | [log] [tgz] |
---|---|---|
author | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Fri Feb 09 18:55:45 2024 -0800 |
committer | ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Sat Feb 10 02:55:58 2024 +0000 |
tree | f5de0cf18eff289b514034cbe15b03875b46b2b0 | |
parent | 2e40e908000b113f0237439ca95c16f4ea093093 [diff] |
Update Metadata Cache Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8756515738972216305 Change-Id: If5de4930569142f70d5b40f70702054e4f6022a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/toolchains/+/5282745 Bot-Commit: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com>
This overlay holds the various CrOS toolchain packages.
There is a single cross-*-linux-*
directory as all of our Linux toolchains use the same underlying packages. This isn't a strict requirement to keep in case we ever want to change or tweak one target, but it makes management a little bit easier.
If you need to update one of the generated configs, use the ./copy_crossdev.sh script to copy the crossdev generated config from /etc/portage into this repo. i.e.,
sudo crossdev --stable --show-fail-log --env 'FEATURES=splitdebug' -P --oneshot --overlays '/mnt/host/source/src/third_party/chromiumos-overlay /mnt/host/source/src/third_party/eclass-overlay /mnt/host/source/src/third_party/portage-stable' --ov-output /usr/local/portage/crossdev -t i686-cros-linux-gnu --ex-pkg sys-libs/libxcrypt --ex-pkg sys-libs/llvm-libunwind --ex-pkg sys-libs/libcxx --binutils '[stable]' --gcc '[stable]' --kernel '[stable]' --libc '[stable]' --ex-gdb --init-target
./copy_crossdev.sh