-
Notifications
You must be signed in to change notification settings - Fork 503
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
windows-bindgen
should generate no_std
bindings by default
#3335
Comments
While we can probably add/update a sample, there's not really much to illustrate here beyond adding |
Actually, I attempted to port a sample to use |
windows-bindgen
should generate no_std
bindings by default
Note to self: |
What I had in mind for a complete no_std sample was things like setting up a panic handler, allocator (if you've actually figured out a way to use no_std with alloc in user space), and any other bits that are required for non-trivial no_std projects on Windows. |
If you mean the If you mean a custom allocator then you may want to look at https://github.com/microsoft/windows-drivers-rs for examples. |
@kennykerr Are you still planning to make the sample_direct2d project no_std as a test case and demo? |
Yes, this issue was mostly resolved by #3359 but I'll open again to address some remaining issues and update the sample. |
Thanks for checking! 🙂 |
@mwcampbell I decided against updating the sample as it butched the sample undesirably, but I fixed the underlying code gen and added tests to ensure that everything should build with Please take #3366 for a spin and let me know if you run into any problems. |
Since the windows crate recently gained support for using no_std while still supporting alloc, it would be useful to have a complete example of an executable or DLL built this way. I read in #3047 that some low-level components, including in Windows itself, use the crate this way. I understand if this is an impractical request because all the real examples are too tightly coupled to Windows's build system or other proprietary bits.
The text was updated successfully, but these errors were encountered: