-
Notifications
You must be signed in to change notification settings - Fork 3
Automatically generate BDWGC bindings #183
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
Conversation
|
Ah, I see what’s happened here. I’ve not taken into account existing BDWGC artefacts in the build directory. |
|
I've pushed some changes that are needed to land this PR. It mainly revolves around pulling BDWGC out of the library/std build.rs script and into the bootstrapper, this is then reused as a dynamic |
|
Please squash. |
|
These commits are logically separate so I think we can leave as-is |
|
Please squash. |
|
Squashed |
|
I've pushed a fix for this here d25db11. The I'll need to rebase this against ToT if you're happy? |
|
Please squash. |
As part of the bootstrap phase, we now search for `src/bdwgc/include/gc.h` and use that to automatically generate Rust bindings. This is less error-prone and means that we can any BDWGC API we wish without having to manually export them one by one.
This works by ensuring that the bootstrap phase puts libgc.so inside the sysroot, where the librustc-driver and libtest objects are already given to search at load time in their RPATH.
|
Squashed |
As part of the bootstrap phase, we now search for
src/bdwgc/include/gc.hand use that to automatically generate Rustbindings. This is less error-prone and means that we can any BDWGC API
we wish without having to manually export them one by one.