rusty_v8/rust-toolchain.toml

[toolchain]
channel = "1.82.0"
components = ["rustfmt", "clippy"]
targets = [
    "x86_64-apple-darwin",
    "aarch64-apple-darwin",
    "x86_64-unknown-linux-gnu",
    "aarch64-unknown-linux-gnu",
    "x86_64-pc-windows-msvc",
    "aarch64-linux-android",
    "x86_64-linux-android",
]
chore: update Rust to 1.65.0 (#1116) 2022-11-25 13:32:52 +00:00			`[toolchain]`
fix: glibc version (#1659) go back to 22.04 to fix glibc version. updates clang for newer features used in v8. also requires a rust toolchain upgrade to build correctly for mysterious and unknown reasons. 2024-11-04 10:08:49 +00:00			`channel = "1.82.0"`
chore: update Rust to 1.65.0 (#1116) 2022-11-25 13:32:52 +00:00			`components = ["rustfmt", "clippy"]`
chore: Fixed incorrect use of cfg! macro and update build.rs to support arm target (#1458) What I've done Fixed incorrect use of cfg! macro use the CARGO_CFG_TARGET_<OS/ARCH> macro instead of the original cfg! (target_<os/arch>) This is because The build script is compiled for the host architecture as a separate build phase, as that's where it runs. Since the cfg macro runs at compile time it'll always report the host configuration there.When cargo runs the build script it passes the configuration through environment variables, one of which is CARGO_CFG_TARGET_ARCH. Some dicussions can be found here update build.rs to support arm target support arm target. Like the Aarch64 target, we need to additionally install the cross-compilation toolchain and specify the linker in Cargo/config.toml. I can add this part of the work in next pull request if necessary. Co-authored-by: Matt Mastracci <matthew@mastracci.com> 2024-05-12 17:00:14 +00:00			`targets = [`
			`"x86_64-apple-darwin",`
			`"aarch64-apple-darwin",`
			`"x86_64-unknown-linux-gnu",`
			`"aarch64-unknown-linux-gnu",`
			`"x86_64-pc-windows-msvc",`
			`"aarch64-linux-android",`
			`"x86_64-linux-android",`
			`]`