Skip to content
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: Adding Support for Android on RISC-V64 Develop #1333

Open
wants to merge 3 commits into
base: develop
Choose a base branch
from

Conversation

MaoHan001
Copy link

Recently, while supporting an Android product based on the RISC-V architecture, we utilized the Mars library and added the relevant compilation support (Google NDK has provided support for RISC-V starting from r27c).

This PR mainly includes three changes:
adding support for the Boost library on RISC-V
adding OpenSSL support on RISC-V
and introducing the compilation target.

The Develop branch appears to have a strong restriction on the NDK version, making it impossible to build based on the r27 version.
The master branch code has been successfully verified for compilation with:
#1332

This change synchronizes RISC-V 64 support from the upstream project at:
https://github.com/boostorg/context/tree/46effe4588a6edd64d49a853454b5f67f7196e57
which introduces assembly implementations for jump_fcontext and
make_fcontext for RISC-V 64 target. The changes include saving
and restoring floating-point and general-purpose registers, setting
up the stack, and handling context switching.
This commit introduces RISC-V 64 architecture support by adding
corresponding configuration file prebuilt static libraries libcrypto.a
and libssl.a.
This commit updates build_android.py to support RISC-V architecture
by adding riscv64 to the strip and STL file paths, and setting the
appropriate API level (android-35) for RISC-V builds.
The -Wno-deprecated-declarations and -Wno-deprecated-builtins options
have been added to suppress warnings generated by newer versions of NDK.
@tencent-adm
Copy link
Member

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@MaoHan001
Copy link
Author

image
CLA is signed but the status is not updated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants