On 1/12/21, Jimmy Brush <[email protected]> wrote: > > Based on these discussions we have started prototyping a > procedurally-generated native rust seL4 library built from a complete > seL4 IDL specification. > > Once we have built this out we intend to share our learnings and > continue to advocate for changes to seL4 and/or upstream work that > improves the experience for everyone building their own language > bindings or dynamic systems on seL4. >
Is there any particular reason why you didn't just port your bindings to feL4? It does use the C bindings underneath (through bindgen), but I don't think that's a big problem, as they don't have much room for memory bugs (and UX/RT is not meant to be a "Rust OS" like Redox and Robigalia; it will just be an OS that has a lot of subsystems written in Rust, but there will still be a lot of third-party C code). It was relatively easy for me to port your old bindings and allocators to my fork of feL4. Here is the UX/RT subproject with the bindings and allocators (rust-bitmap, rust-sel4, and sel4-alloc are forked from Robigalia; the rest is from feL4 except for sel4-slabmalloc): https://gitlab.com/uxrt/core-supervisor/fel4/ _______________________________________________ Devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
