Error:

/claves/target/debug/build/apple-sys-2c839338cff8c061/out/Carbon.rs:56522:5
      |
56520 | #[derive(Debug)]
      |          ----- in this derive macro expansion
56521 | pub struct IORPCMessageErrorReturnContent {
56522 |     pub hdr: IORPCMessage,
      |     ^^^^^^^^^^^^^^^^^^^^^ `IORPCMessage` cannot be formatted using `{:?}`
      |
      = help: the trait `Debug` is not implemented for `IORPCMessage`
      = note: add `#[derive(Debug)]` to `IORPCMessage` or manually `impl Debug for IORPCMessage`
      = note: this error originates in the derive macro `Debug` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider annotating `IORPCMessage` with `#[derive(Debug)]`
      |
56510 | #[derive(Debug)]
      |

For more information about this error, try `rustc --explain E0277`.
error: could not compile `apple-sys` due to previous error

OS: MacOS 13.0.0

When compiling apple-sys v0.1.2 as a dependancy with stable-aarch64-apple-darwin 1.67.1 on Apple Silicon M2 Pro I get the following error:

error[E0277]: `IORPCMessage` doesn't implement `Debug`
     --> /Users/linus/CLionProjects/coconut-ctrl/target/release/build/apple-sys-9c941ba7ed467999/out/IOKit.rs:55699:5
      |
55697 | #[derive(Debug)]
      |          ----- in this derive macro expansion
55698 | pub struct IORPCMessageErrorReturnContent {
55699 |     pub hdr: IORPCMessage,
      |     ^^^^^^^^^^^^^^^^^^^^^ `IORPCMessage` cannot be formatted using `{:?}`
      |
      = help: the trait `Debug` is not implemented for `IORPCMessage`
      = note: add `#[derive(Debug)]` to `IORPCMessage` or manually `impl Debug for IORPCMessage`
      = note: this error originates in the derive macro `Debug` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider annotating `IORPCMessage` with `#[derive(Debug)]`
      |
55687 | #[derive(Debug)]
      |

for apple-bindgen not apple-sys

apple-bindgen --sdk /Users/user/Downloads/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS.sdk CoreHaptics
/Users/user/ch2/CoreHaptics.h:1:9: fatal error: could not build module 'CoreHaptics'
thread 'main' panicked at 'binding generation failed: ClangDiagnostic("/Users/user/ch2/CoreHaptics.h:1:9: fatal error: could not build module 'CoreHaptics'\n")', /Users/user/.cargo/registry/src/github.com-x/apple-bindgen-0.2.0/src/main.rs:69:34
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

See https://github.com/segevfiner/keepawake-rs/actions/runs/4272014787/jobs/7436882628

 error[E0119]: conflicting implementations of trait `Debug` for type `IORPCMessage`
     --> /Users/runner/work/keepawake-rs/keepawake-rs/target/aarch64-apple-darwin/release/build/apple-sys-7a498b7b0123b7f9/out/IOKit.rs:55036:10
      |
55036 | #[derive(Debug)]
      |          ^^^^^ conflicting implementation for `IORPCMessage`
...
82951 | impl ::std::fmt::Debug for IORPCMessage {
      | --------------------------------------- first implementation here
      |
      = note: this error originates in the derive macro `Debug` (in Nightly builds, run with -Z macro-backtrace for more info)

Greetings @youknowone

I fairly recently completed an initial version of icrate over at the objc2 project, and wanted to tell you about it, as you seem to be doing a lot of the same in this project.

The desire with icrate is basically to be your one-stop-shop for all of Apple's frameworks, but importantly, with correct memory management and type-safety.

A few differences between apple-sys:

• The bindings are generated beforehand, so that the user doesn't have to run clang in their build script, and so that we can support docs.rs
• I went with creating the binding generator from scratch instead of using bindgen, since there were just too many things that would need changing to support (to name two things, multiple architectures in the same repo, and a nice file diff). In any case, the binding generator implementation is an implementation detail, and I actually intend to change it again
• I have something similar to Bindgen.toml called translation-config.toml. But for the most part, the intention is that fixes are implemented in normal Rust code, instead of imbedded in that file.

Feel free to ask me any questions if there's something I haven't fully explained!

(I discovered your project a little while ago when researching names for icrate, and didn't really think much of it then, but I see that you are still active here, so I figured I would try to recruit you - or at the very least, get input from you if icrate doesn't suit your needs ;) ).