| commit | b630b6e03f683219275c8a27092d3e5a39b1e769 | [log] [tgz] |
|---|---|---|
| author | chromeos-ci-prod <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Mon Apr 01 16:23:12 2024 -0700 |
| committer | ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com> | Mon Apr 01 23:23:28 2024 +0000 |
| tree | 29713ccab36aba15a3ef5bd4f7f8fdcb6db9442a | |
| parent | 37ee786bbedfc1b6a88486f7a5ffc1582d40675e [diff] |
Update Metadata Cache Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8751818035551288385 Change-Id: I7a5505383823ff82f1dc2bdaef2fd08ddc8f17f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/toolchains/+/5409219 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