Jonathan Schwender

> It converts e.g. flags-lib into flags_lib Ah, I see. No that is not intended. In that case lets stick with the `string(REPLACE)`. Sorry for confusion.

>For example, can I change cxxbridge-cpp Yes, that name was arbitrary. Please do note that the cxxbridge integration is still considered experimental, and is not yet available in any official...

> Also passing the cflags is necessary, as it may define the ABI (e.g. hard float on arm) There are also `CXX_FLAGS`, `$_FLAGS_$` and c flags set as target properties....

> I've read that this is possible to have multiple cxx rlib, one rust static library that does extern crate thingy. Until the `rlib` format is stabilized for external linker...

I ran into this when building servo / [mozangle](https://github.com/servo/mozangle/issues/76) on ubuntu with both clang (clang-14) and clang-15 installed. `libclang-sys` will take the most recent `libclang` version, while bindgen will take...

I'm wondering what the current status is here, is this PR blocked waiting on a review?

Are you sure you made this issue in the right repo? Your log in the bugzilla points to nss-gk-api, and the [build-script](https://github.com/mozilla/nss-gk-api/blob/main/build.rs) of that crate uses [bindgen](https://github.com/rust-lang/rust-bindgen), not cbindgen. Note:...

> I was initially curious about the stability of this feature given the ⚠️⚠️⚠️ EXPERIMENTAL ⚠️⚠️⚠️ warning in [the docs](https://corrosion-rs.github.io/corrosion/ffi_bindings.html#cxx-integration) but if we're vendoring this part I suppose it's less...

I just ran into this and in my case it was caused by the following code: ```rust let array: [UnsafeCell; NE]= unsafe { MaybeUninit::uninit().assume_init() } ``` For the standard library...

> Note: It has a dependency on both the Rust compiler (cargo) and a C++ compiler. Corrosion maintainer here. Just to clarify, a C++ compiler is not required from Corrosions...