cmake-rs
cmake-rs copied to clipboard
Rust build dependency for running cmake
## 🤖 New release * `cmake`: 0.1.51 -> 0.1.52 Changelog ## [0.1.52](https://github.com/rust-lang/cmake-rs/compare/v0.1.51...v0.1.52) - 2024-08-23 ### Other - Add a `success` job to CI - Change `--build` to use an absolute...
Building the test crate has this error: ``` In file included from /cargo/registry/src/index.crates.io-6f17d22bba15001f/libz-sys-1.1.19/src/zlib-ng/arch/x86/adler32_avx512.c:17:0: /cargo/registry/src/index.crates.io-6f17d22bba15001f/libz-sys-1.1.19/src/zlib-ng/arch/x86/adler32_avx512_p.h: In function '_mm512_reduce_add_epu32': /cargo/registry/src/index.crates.io-6f17d22bba15001f/libz-sys-1.1.19/src/zlib-ng/arch/x86/adler32_avx512_p.h:22:1: error: unrecognizable insn: } ^ (insn 12 11 13 2 (set (mem/c:V4DI...
I ran into an issue where the makefiles of the C dependency I'm building assumed an x86_64 architecture because cmake-rs sets the toolset flag to `x64` [here](https://github.com/rust-lang/cmake-rs/blob/c4a60dd154dd90e469dffc41a1faa717704f90b3/src/lib.rs#L651-L653), even on aarch64....
Currently it's possible to skip the "target" step (`install` by default), but it's not possible to skip the `cmake --build` invocation (i.e., to _only_ run configure). It'd be nice if...
Up until now the cc-rs crate only ever used patch releases, Though they now moved on to v1.1.x .
To ensure that nothing accidentally gets broken, we could use some more tests that exercise all of the config options.
Is there a way to get / show progress bar percentage? I build some c++ library which takes some time, and it would be nice to see the progress percentage...
Hello I've noticed some issues when using cmake-rs to build a project for the wasm32-unknown-emscripten target: 1- Build failure when the host is windows: ``` thread 'main' panicked at C:\Users\runneradmin/.cargo\registry\src\index.crates.io-6f17d22bba15001f\cmake-0.1.51\src/lib.rs:1100:5:...
Added a set of methods to implement something similar to `no_default_flags` in the `cc` crate. Issue here #198
This references #223 It utilizes the Emscripten.cmake toolchain file (as cmake-rs already does for android). The location is determined via the EMSDK env variable, or EMSCRIPTEN_ROOT or em-config which should...