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

[DOC] NDK compatibility table #1760

Closed
DanAlbert opened this issue Sep 1, 2022 · 7 comments
Closed

[DOC] NDK compatibility table #1760

DanAlbert opened this issue Sep 1, 2022 · 7 comments
Labels

Comments

@DanAlbert
Copy link
Member

URL

new page, probably

Problem

Forking from the bazel thread. I don't think we have such a thing, but probably should.

Unless you're talking about extremelely old devices (close to a decade), r25 works just fine. r25 was actively tested against KitKat.

@oakad do you have a particularly old device in mind? Older than KitKat? Perhaps we need a clearer FAQ or table explaining how NDK releases, API levels, OSes, and devices are all related and the various levels of compatibility? Maybe with some example devices?

Originally posted by @jiawen in bazelbuild/bazel#12889 (comment)

@DanAlbert DanAlbert added the docs label Sep 1, 2022
@DanAlbert DanAlbert added this to the unscheduled docs milestone Sep 1, 2022
@oakad
Copy link

oakad commented Sep 2, 2022

Actually, it seems we will stop supporting all pre-Lollipop devices this year.

So, older than KitKat is no longer a problem.

(Kind of funny how it is a struggle to stop supporting Android 4.x in 2022 :-)

@EwoutH
Copy link

EwoutH commented Oct 2, 2022

Great idea, I will love to see a NDK compatibility table somewhere in the documentation!

@DanAlbert
Copy link
Member Author

All this info is already available, FWIW. It just isn't consolidated across NDKs into one location. The changelogs will tell you when an API level loses support, and the meta/platforms.json file contains that information for each NDK.

@EwoutH
Copy link

EwoutH commented Oct 4, 2022

It just isn't consolidated across NDKs into one location.

This would add value and is the point of this issue, I think.

@DanAlbert
Copy link
Member Author

Agreed, just checking.

@cederom
Copy link

cederom commented Oct 17, 2022

+1 :-)

@DanAlbert
Copy link
Member Author

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

No branches or pull requests

4 participants