Open cnwzhjs opened 11 months ago
@cnwzhjs it seems the new code is not formatted with rustfmt. Can you run cargo fmt
and commit the changes?
@cnwzhjs it seems the new code is not formatted with rustfmt. Can you run
cargo fmt
and commit the changes?
Sure, I'll do that as soon as confirming of how we handle the acl/attr dependencies
Hi @elBoberido , I've just force updated the branch to fix the issues:
libacl
and libattr
and their build scripts@cnwzhjs I'll have a closer look to it later on but could you also add a new CI job for cross compiling? Just to ensure we don't break it in the future.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 49.87%. Comparing base (
fdd6495
) to head (adbdc75
). Report is 5 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Looks good. Just a few nitpicks :)
Once the cross compile CI is set up this can be merged
Hi @elBoberido , I've updated the code according to your advices, thanks a lot.
Talking about continuous integration, I need your advice as well:
As you know, cross compiling to aarch64 requires a sysroot with all header and libraries in aarch64. In my local environment, I wrote a script to download, and extract these files from deb packages from debian or ubuntu repository to prepare this sysroot.
Should we include these scripts within the repo, or do you have any other advice on this.
Talking about continuous integration, I need your advice as well:
As you know, cross compiling to aarch64 requires a sysroot with all header and libraries in aarch64. In my local environment, I wrote a script to download, and extract these files from deb packages from debian or ubuntu repository to prepare this sysroot.
Should we include these scripts within the repo, or do you have any other advice on this.
Having to extract files from debian packages sounds cumbersome and might easily break. Did you check these sources?
Talking about continuous integration, I need your advice as well: As you know, cross compiling to aarch64 requires a sysroot with all header and libraries in aarch64. In my local environment, I wrote a script to download, and extract these files from deb packages from debian or ubuntu repository to prepare this sysroot. Should we include these scripts within the repo, or do you have any other advice on this.
Having to extract files from debian packages sounds cumbersome and might easily break. Did you check these sources?
https://github.com/marketplace/actions/cross-compile-support-on-ubuntu
- maybe get inspiration from their action.yaml
- https://github.com/marketplace/actions/build-rust-projects-with-cross
- https://github.com/marketplace/actions/setup-toolchains-for-cross-compilation-and-cross-testing-for-rust
- https://superuser.com/questions/1738940/install-arm-librariers-including-dependencies-on-amd64
Thank for th reply. The first link seems to be clean and work, I'll give it a try.
@cnwzhjs just wanted to know if you are till working on this PR
Pre-Review Checklist for the PR Author
rustfmt
iox-123-this-is-a-branch
)iox-#42 commit text
)task-list-completed
)Notes for Reviewer
Currently only toolchain file for target
aarch64-unknown-linux-gnu
is added. If anyone has a test platform for other targets, please add them as well.Checklist for the PR Reviewer
Post-review Checklist for the PR Author
References