-
Notifications
You must be signed in to change notification settings - Fork 50
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
feat: support openharmony platform #434
Conversation
Are there any tools (similar to cross-rs or cargo-xwin) that would allow us to test compilation to an OpenHarmony target in our CI? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #434 +/- ##
==========================================
- Coverage 95.80% 92.67% -3.13%
==========================================
Files 61 61
Lines 8143 8174 +31
Branches 0 8174 +8174
==========================================
- Hits 7801 7575 -226
- Misses 342 357 +15
- Partials 0 242 +242 ☔ View full report in Codecov by Sentry. |
No, in fact, there is currently no very suitable way to run code whose target architecture is openharmony, even rust or openharmony officially does not have it yet. When there is a suitable way, I will try to add the corresponding CI to support |
6e5ae0f
to
0e31dc3
Compare
Issues:
Description of changes:
When using cmake for building, make sure to include the cmake files and parameters that openharmony needs to ensure a successful build.
Call-outs:
Point out areas that need special attention or support during the review process. Discuss architecture or design changes.
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? Are there any testing steps to be verified by the reviewer?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.