-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate bindings for each target #7
Conversation
Hmmmm, yeah, I agree we should do the platform specific generated code. I wonder if there's a relatively simple way we could only put truly platform-specific code in the individual platform files and share the other 99%, partly to avoid needing to commit 145K lines of code 😬 |
7e43de0
to
f3527b9
Compare
@quinnj This is RTM for me. I had to ignore some ITT API symbols that aren't useful to us. |
gen/Manifest.toml
Outdated
uuid = "73048d1d-b8c4-5092-a58d-866c5e8d1e50" | ||
version = "0.9.14+0" | ||
version = "0.9.3+1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like this slipped back again
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I bumped it back up and re-ran the generation, which was good for me to try out locally anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, not sure how that happened
As far as I understand it, we need to generate bindings per-target because the JLL contains header files per-target and they could differ.
I would rather be safe than sorry.