Skip to content

Releases: rust-lang/cc-rs

1.0.77

20 Nov 22:56
Compare
Choose a tag to compare

Version 1.0.77

Changelog

  • Added a new Build::asm_flag function, which allows providing flags that are only used when compiling assembly files (for example, if your C compiler rejects flags passed to the assembler when not used as an assembler). (#752)
  • Ensure that the version of DWARF debuginfo we emit is consistent with what rustc uses on the given target. (#694)

Thanks to everybody who contributed to this release!

1.0.76

08 Nov 23:39
Compare
Choose a tag to compare

Version 1.0.76

Changelog

  • When compiling with clang-cl, we now only use -- to separate flags/options from input files when not using the assembler, which doesn't support that option. This is a fix for a regression introduced in 1.0.74 (by #514) (present in 1.0.75 as well). (#747)

This is essentially a bugfix release, so that's all!

1.0.75

08 Nov 16:45
Compare
Choose a tag to compare

Version 1.0.75

Changelog

  • When Rust debuginfo is enabled, debuginfo is passed to MSVC assemblers (#742)
  • When locating an ar executable, *-ar is now preferred to *-gcc-ar (#741)
  • On MSVC 15+, the atlmfc directory is now correctly located (#699)

Additionally, a number of smaller changes which shouldn't impact users have been made; see the commit history for complete details.

Thanks to everybody who contributed to this release!

1.0.74

29 Oct 14:04
d053161
Compare
Choose a tag to compare

Version 1.0.74

Changelog

  • When compiling with clang-cl, we now use -- to separate flags/options from input files. (#514)
  • We now fall back to RUSTC_LINKER's prefix (rather than erroring) if we fail to determine the prefix to use for the given target. (#685)
  • A Build::link_lib_modifier function was added to allow control which library modifiers are used when linking with the generated library. (#671)
  • When searching for an ar binary to use, we now try {target}-ar in addition to {target}-gcc-ar. If they're both present, {target}-ar will be preferred. (#735, #736)
  • We now emit cargo:rerun-if-env-changed messages for environment variables that influence the build. This is only done if cargo_metadata is enabled, and can be disabled by passing false to the new Build::emit_rerun_if_env_changed builder function. (#701, #738)

New Targets

The following targets are now supported:

  • The Apple WatchOS (and simulator) targets (*-watchos and *-watchos-sim). (#662)
  • The LLVM-based MinGW targets (*-pc-windows-gnullvm). (#734)
  • The Xous microkernel (riscv32imac-unknown-xous-elf). (#686)

Additionally, a number of smaller changes which shouldn't impact users have been made; see the commit history for complete details.

Thanks to everybody who contributed to this release!