Linking against private frameworks?

[NyaomiDEV]

I wonder if it is inside the scope of this project to be able to link against private frameworks (specifically MediaRemote) and to use them in a mostly-type-safe way.

[silvanshade]

There has been a little discussion around being able to use the header-translator (the tool icrate uses to generate the Rust definitions from the Apple frameworks) for other frameworks. For example, see item 2 at #429.

So far there hasn't been a lot of work toward making this practical though. In principle, I believe it should be possible now, but it would require some modification to the icrate configuration and potentially to some parts of header-translator.

The situation should improve in the next few months hopefully, once there has been more progress made toward the new dependency scanning backend.

[madsmtm]

At some point after #345 we'll probably figure out a good way for translating headers not provided via. Xcode, then you should be able to just run header-translator (or whatever it'll end up being named) on your header and get a Rust library that targets that.

[madsmtm]

Oops, @silvanshade beat me to it, but agree with everything they said

[madsmtm]

My current plan is to work on improving bindgen's Objective-C support, see #729. Once that is done, you'd be able to use bindgen to map the private framework. So I'll close this issue in favour of that one.

It might be possible to do it today using header-translator, but I don't really want to support such use-cases.

Another option in the meantime would be to manually author the bindings you need using the extern_class!, extern_methods! and extern_protocol! macros that objc2 provides.