commit | c52f0082a0bd8703e9cc6dbd711b69349929d9e5 | [log] [tgz] |
---|---|---|
author | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Mon Jan 22 10:03:52 2024 -0800 |
committer | ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Mon Jan 22 18:04:00 2024 +0000 |
tree | e58c21e308b38afd98184d6ae22a83223c3571c0 | |
parent | 5fd51e1ca4162e3ca1af0afd34b79329d6382978 [diff] |
Update Metadata Cache Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8758179631408927089 Change-Id: Ief68f598ad74f3a74faf33e688b6d60b41cc4063 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/toolchains/+/5225881 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