Dan Albert

Revisiting this, this should probably be done in the driver so it's not unique to our build systems. A bit late to do that for r27, so retriaging to r28.

Some prior discussion: https://github.com/android/ndk/discussions/1692 Tl;Dr, no plans.

No change since my last comment. It's open because it's a reasonable request that has yet to become a priority.

Hmm. I'd like to fix this in r26 but that particular component has gotten tricky to update now that rv64 is in the development branch. It isn't a regression in...

> Generating from canary might be more worrisome if that includes possibly unstabilized/unfinished APIs? The data needed to avoid those is there (`__attribute__((availability))`), but you're probably right that cbindgen doesn't...

For most APIs (doesn't work for libc/libm because reasons) you need https://android.googlesource.com/platform/ndk/+/master/docs/BuildSystemMaintainers.md#Weak-symbols-for-API-definitions or the decl will be hidden from cbindgen.

> Not sure if you're aware and/or adding a CI process to check that all headers are C-compliant, so mentioning it here. We tried, but the build systems we have...

> without spawning a totally new issue for a simple question Don't hesitate to use the "discussions" tab. That's what it's there for :) > where can I find what...

>> More generally, "what's going to be in the next release?" is answered in the projects tab. There's no secret internal planning board; that board is the real one. >...

> the one I've uploaded at https://android-review.googlesource.com/c/platform/frameworks/native/+/2897863 remains untouched for 2 weeks 👎 You've added no reviewer. Doubtful anyone was notified (subscribing to all new changes in frameworks/base would probably...