| commit | 92a9aeead1fc1990ea0786a66a9916eb9fa91193 | [log] [tgz] |
|---|---|---|
| author | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Wed Oct 30 21:20:36 2024 -0700 |
| committer | ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Thu Oct 31 04:20:43 2024 +0000 |
| tree | ece274ba9d35d4c2fd2f12842df9f44f69de5b76 | |
| parent | 9a5fe0fad1ff25f3642bb4ae65a133bf0bc74804 [diff] |
Update Metadata Cache Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8732592411226851441 Change-Id: I1de08375a4689f0b4f09b47e51e452ac89d829c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/toolchains/+/5980793 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.shIf you're adding a new package, ./copy_crossdev.sh will do most of what you want. You may need to add a symlink to the package under the triples you want to support, though. e.g.,
cd cross-x86_64-cros-linux-gnu && ln -s ../../chromiumos-overlay/dev-lang/rust