DemesneGH commented on issue #66: URL: https://github.com/apache/incubator-teaclave-trustzone-sdk/issues/66#issuecomment-1078735978
Hi @syedelec > is it possible to use the latest nightly version (`nightly-x86_64-unknown-linux-gnu`) ? Yes but not yet. When upgrading toolchains, the std should be upgraded to a proper version at the same time. Because the std code can only be compiled in a certain range of versions of the Rust toolchain. > why not the stable version (`stable-x86_64-unknown-linux-gnu`)? No. The nightly version is needed for building customized std. > Also why install xargo from specific 1.44.0 version and not use the stable/nightly version The toolchain for installing xargo can be upgraded to a newer version but we've not tested for it. > Finally, the source code is for rust, compiler-builtins and libc are taken from https://github.com/mesalock-linux org and these specific repos seems not updated. It would be great if the repos could be updated to a stable version and apply the single commit on top to get it working. The rust, compiler-builtins and libc ported for OP-TEE are based on the stable Rust version 1.56.1. And the patch for OP-TEE is in https://github.com/mesalock-linux/rust/commit/6abda667852184641149d34da4730d96ba4f7d31. > these are suggestions and I would like to know if this is doable because I may get into it to clean repos and make it working with minimal workarounds. For simplification of the building environment, one considerable way is to add the `aarch64-unknown-optee-trustzone` target into the upstream Rust compiler repo. Then we can build binaries for this target by `rustup target add aarch64-unknown-optee-trustzone`. But this needs more work to integrate the customized std into the Rust repo. What are your needs for the minimal building environment? Any thoughts would be appreciated. Thanks Yuan -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
