| commit | 29233e35415bb4519fd766141b9f7167bd262fac | [log] [tgz] |
|---|---|---|
| author | Daniel Wagner-Hall <dwagnerhall@apple.com> | Tue Nov 29 11:34:25 2022 +0000 |
| committer | GitHub <noreply@github.com> | Tue Nov 29 11:34:25 2022 +0000 |
| tree | 4fd806b543ffc6016a94273b4b918453f5517db0 | |
| parent | ed32b6de26118eecf207b7d33c8a4fc31848e0e3 [diff] |
Revert #1564 (#1663) * Add example workspace cross-compiling with zig We've run into a number of issues, both in rustc and in cargo build scripts, where we're not properly propagating cc_toolchain information to compiles and particularly link actions. These have often been hard to test because we don't have an example set-up with a non-default C++ toolchain. By wiring up a zig cross-compiling toolchain, we have a concrete example we can work with. It's also an interesting potential example for folks who want to set something similar up. * Revert #1564 It looks like the reported issue is probably related to the ios toolchain in use, rather than our general toolchain flag propagation. * Add platform_mappings and --cpu flag to ios_build example
This repository provides rules for building Rust projects with Bazel.
General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust.
Please refer to the full documentation.