How to build executorch with ANDROID_ABI=armeabi-v7a
Open
Nobody has claimed this yet.
module: build/install
triaged
- Dominant language
- Python
- Stars
- 5k
- Forks
- 1.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 581
Description
🚀 The feature, motivation and pitch
https://github.com/pytorch/executorch/blob/main/tools/cmake/Utils.cmake#L89
here, there is no "ANDROID_ABI=armeabi-v7a" option, so if i want to build executorch for ANDROID_ABI=armeabi-v7a, how to do?
thank you very much
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
cc @larryliu0820 @jathu
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at tools/cmake/Utils.cmake around line 89 and trace how Android ABI values are accepted during the Executorch build. Check the existing build documentation and Android configuration entry points; the work is complete when the supported path for armeabi-v7a is documented or the requested support is clearly scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cmake
- Domain
- build-system, mobile-dev
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100