DemesneGH commented on issue #113: URL: https://github.com/apache/incubator-teaclave-trustzone-sdk/issues/113#issuecomment-1824085581
Thanks for sharing valuable insights! > I am also leaning towards supporting `no_std` TAs (target: `aarch64-unknown-none`) for OP-TEE given there are many crates supporting `no_std` features too. I agree that there are many crates supporting `no_std` features, but supporting `std` is necessary for other crates, such as `Rustls` (a widely used TLS crate). Porting std expands the range of crates available, would be more friendly for developers. > Are there any plans to make it an official target upstream? To streamline maintenance efforts, we've chosen to pin the Rust version and port the std library. Adding the target to Rust upstream is a reasonable and aligns with future plans. > I think most of the target 'aarch64-unknown-teeos' and 'aarch64-unknown-optee-trustzone' are the same. But op-tee may want a more specific name. > So if we really need to support `std` library then it should be a different target. Agree. If the target is eventually added to the upstream, I would prefer to maintain the name `aarch64-unknown-optee-trustzone` for consistency. > I have some experience with what need to implement Thanks for sharing the experience of upstream`aarch64-unknown-teeos`, it will be good reference for us. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@teaclave.apache.org For additional commands, e-mail: dev-h...@teaclave.apache.org
