DemesneGH commented on PR #114:
URL: 
https://github.com/apache/incubator-teaclave-trustzone-sdk/pull/114#issuecomment-1870911115

   > The CI reports `No space left on device`, are there any space constraints 
for CI?
   
   The Github actions provide at least 14G storage (reference: 
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources).
 It would be more than 14GB sometimes 
(https://github.com/actions/runner-images/issues/2840#issuecomment-791177163) 
since the error haven't occurred before.
   
   There are some workaround on 
https://github.com/actions/runner-images/issues/2840#issuecomment-790492173 but 
I'd prefer to remove the dependencies of `aarch64-unknown-optee-trustzone` 
target (large clones in setup.sh).
   
   -----------
   I'm trying to summarize the conclusions we reached and the steps for 
breaking down, please correct me if I've misunderstood:
   
   STAGE 1:
   1. keep the `no-std` a separate branch from `master`.
   2. publish the optee-utee crate on crates.io. The `optee-utee` crate is 
`no-std` by default, corresponding to `no-std` branch on repo. Users can import 
the crate using `cargo add optee-utee`.
   3. When users need the `std` , they should clone the SDK repo of `master` 
branch and setup the environment.
   
   comments:
   - for `no-std` branch:
   1. Recommend removing all `aarch64-unknown-optee-trustzone`target related 
files such as `aarch64-unknown-optee-trustzone.json`,  
`arm-unknown-optee-trustzone.json`, `environment`, and `std`-only `examples`. 
It makes things clear and also helps us to figure out the difference when we 
trying to merge the `no-std` branch at STAGE 2. (BTW it's also the workaround 
for the `no space left` issue above)
   
   - for publishing optee-utee crates:
   1. todo:  support for inter-TA APIs
   2. Aiming that users use the `optee-utee` crate with just `cargo add`, we 
may need a `build.rs` inside the `optee-utee` crate which download toolchains, 
optee c source code and compile c libs.
   
   STAGE 2 (after the STAGE 1 is finished):
   - for master branch:
   1. merge the new released `optee-utee` crate (enable the `std` feature)
   2. proceed `aarch64-unknown-optee-trustzone` uprev
   3. consider merging the `no-std` into `master`


-- 
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

Reply via email to