-
Notifications
You must be signed in to change notification settings - Fork 63
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
Add optee-utee-build crate #156
Conversation
Split these into separate commits and also add documentation as a separate commit to describe APIs exposed by
I suppose it's independent of this PR which is something @DemesneGH should be able to fix in the dockerfile with required dependencies for CI. We want to keep testing with latest OP-TEE mainline build rather than sticking to a stable release. |
@b49020 May I ask what the documentation you points to, the README.md or the comments in rust codes? |
I will suggest to create a dedicated document titled something like "Tutorial: Writing Rust TAs using optee-utee-build" under https://github.com/apache/incubator-teaclave-trustzone-sdk/tree/main/docs |
Sure, I'm working on that. |
I still have some changes to make and I am writing the document of how to use this crate, everything should be done in 3 days, so we can pause reviewing this PR and wait until I am finish with it. |
@b49020 @DemesneGH PR fixed. |
Update to remove the confusing extra properties of |
The PR for CI fix: #157. |
update to use latest ci |
5f6e455
to
f59a40a
Compare
Thanks @ivila for your efforts addressing review comments, the last one pending for me is here. With that addressed, feel free to add:
|
Once this PR gets merged, let's make all the examples to use |
Is there anything I miss? I think this PR is inactive for a long time.😐 |
65f9a5c
to
d6792ba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After some minor recommendations resolved please feel free to add: Reviewed-by: Yuan Zhuang <[email protected]>
1. introduce build method to make building process simpler. 2. introduce Builder struct for developers who want to customize the building process. 3. introduce HeaderFileGenerator struct for developers who want to generate a header file only. 4. introduce Linker struct for developers who want to handle linking stuff only. Signed-off-by: ivila <[email protected]> Reviewed-by: Sumit Garg <[email protected]> Reviewed-by: Yuan Zhuang <[email protected]>
update to add reviewer |
Thanks! Will merge after the CI passed. |
@ivila CI failed because:
|
Sorry about that, I always miss the |
1. add optee-utee-build in build-dependencies 2. remove uuid from build-dependencies 3. use build method from optee-utee-build instead of custom build script 4. use gcc as linker instead of ld.bfd to avoid compilation problems on Arm host 5. remove ta_static.rs file 6. remove configuration consts in src/main.rs Signed-off-by: ivila <[email protected]> Reviewed-by: Sumit Garg <[email protected]> Reviewed-by: Yuan Zhuang <[email protected]>
1. add document "Writing Rust TAs using optee-utee-build" 2. suggest developers using optee-utee-build in "Migrating to new building env" 3. add description about the supported host machines in README.md Signed-off-by: ivila <[email protected]> Reviewed-by: Sumit Garg <[email protected]> Reviewed-by: Yuan Zhuang <[email protected]>
update to fix the |
FYI the |
this PR relates to #155, and should resolves #135 too.