Skip to content

Investigate cross-compilation to Linux on Aarch64 #300

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.

Sign up for GitHub

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

Jump to bottom
Closed
hug-dev opened this issue Dec 9, 2020 · 4 comments · Fixed by #355
Closed

Investigate cross-compilation to Linux on Aarch64 #300

hug-dev opened this issue Dec 9, 2020 · 4 comments · Fixed by #355
Assignees
@ionut-arm
Labels
documentation ecosystem Issues related to building or improving compatibility layers to enhance Parsec's ecosystem position platforms Compatibility with different secure services or hardware platforms small Effort label

Comments

@hug-dev
Copy link
Member

hug-dev commented Dec 9, 2020

We should provide an easy way and steps how to cross-compile Parsec to the aarch64-unknown-linux-gnu target.

See #55 for history.
@hug-dev hug-dev added the platforms Compatibility with different secure services or hardware platforms label Dec 9, 2020
@ionut-arm ionut-arm added documentation ecosystem Issues related to building or improving compatibility layers to enhance Parsec's ecosystem position small Effort label labels Feb 3, 2021
@ionut-arm ionut-arm self-assigned this Feb 3, 2021
@ionut-arm
Copy link
Member

Assigning this to myself since I've been doing some work on this for the Trusted Service provider

@ionut-arm ionut-arm mentioned this issue Feb 3, 2021
Closed
@hug-dev
Copy link
Member Author

hug-dev commented Mar 5, 2021

It'd be good to test with armv7-unknown-linux-gnueabihf as well (Raspberry Pis).

@hug-dev hug-dev linked a pull request Mar 10, 2021 that will close this issue
Add some cross-compilation tests #355
Merged
@hug-dev
Copy link
Member Author

hug-dev commented Mar 10, 2021

#355 adds cross-compilation tests for Mbed Crypto and PKCS11 provider. Making the TPM provider cross-compilation test is a bit harder because one needs to first cross-compile the TSS libraries and configure pkg-config correctly to point to the cross-compiled version instead of the host one.

I would say what is remaining to do:

  • add something in the book to explain how to cross-compile, what's working
  • add the relevent issues on the tss-esapi crate to support cross-compilation

@hug-dev
Copy link
Member Author

hug-dev commented Mar 10, 2021

For the book: parallaxsecond/parsec-book#90
For the tss crate: parallaxsecond/rust-tss-esapi#204

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ionut-arm ionut-arm

Labels
documentation ecosystem Issues related to building or improving compatibility layers to enhance Parsec's ecosystem position platforms Compatibility with different secure services or hardware platforms small Effort label
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add some cross-compilation tests hug-dev/parsec
2 participants
@hug-dev @ionut-arm