Niklas

Yeah, I'm sorry I didn't provide a reproducible example. Maybe an [issue template](https://blog.github.com/2016-02-17-issue-and-pull-request-templates/) could serve as a gentle reminder to future bug reporters. A reduced test case to reproduce my...

According to the documentation `[export.include]` only adds things (and doesn't work like a whitelist): ``` # A list of additional items to always include in the generated bindings if they're...

Imagine that I have something like this in my crate: ``` #[cfg(feature = "platform-a")] pub mod a; #[cfg(feature = "platform-b")] pub mod b; #[cfg(feature = "platform-c")] pub mod c; ```...

cool, that might be exactly what we need. I'll try it out

I tested it, and it doesn't work exactly as I hoped. Is it possible tto generate `#if PLATFFORM_A == 1` instead? Relying on `defined()` has bitten us in the past,...

Now I noticed that you cannot have `includes` that depend on features. (i'll open new issues for things I run into)

Thanks, with those two workarounds it works OK for us for now. [This](https://github.com/digitalbitbox/bitbox02-firmware/blob/master/src/rust/bitbox02-cbindgen.toml) ended up being our final cbindgen config. * Would you want better support for these usecases? *...

I have the same issue, I have multiple flavors of my android app and expo cannot launch the right one. I tried setting `scheme` in `app.config.js` but that doesn't work...

Would it be possible to use `core_io` with a stable compiler?

Couldn't we always print the default values during reconfigure? That way you would notice that "these are not the default values i expected". If we implement option 2 in OP,...