1.0.79

Version 1.0.79

Changelog

• The riscv32imc-esp-espidf target is now supported (#776)
• Build::is_flag_supported now checks the exit status of the compiler in addition to stderr output, improving reliability (#757)
• When building for the aarch64-apple-ios-sim target -arch arm64 is now correctly passed as two arguments instead of one (#759)
• Improved control over ar and ranlib (#763)
  • New functions to return the ar (Build::get_archiver) and ranlib (Build::get_ranlib) binaries used for this build have been added.
  • Several related environment variables involving the archiver and ranlib variant (ARFLAGS, RANLIBFLAGS, AR, and RANLIB) are now respected automatically if not overridden.
  • Some other changes too, see #763 for details.
• We will now correctly locate msbuild under VS2022 (#773)

---

Additionally, a number of smaller changes which shouldn't impact users have been made (in particular #769 and #777); see the commit history for complete details.

Thanks to everybody who contributed to this release!

1.0.78

Version 1.0.78

Changelog

• Now, only .asm files are passed to masm on windows targets, bringing things back in line with how cc-rs<1.0.77 handled it (#755).
• Absolute paths in source are now mapped as relative in OUT_DIR (#684)
• Several improvements were made to CUDA support (#712)
• llvm-lib.exe is now used instead of lib.exe when clang-cl is used in an MSVC environment (#758)

---

Thanks to everybody who contributed to this release!

1.0.77

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

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

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

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!