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

Unable to use android_ndk_repository rule #13191

Closed
oakad opened this issue Mar 10, 2021 · 3 comments
Closed

Unable to use android_ndk_repository rule #13191

oakad opened this issue Mar 10, 2021 · 3 comments
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: feature request

Comments

@oakad
Copy link

oakad commented Mar 10, 2021

Bazel v4.0.0/Linux

Upon specifying an android_ndk_repository rule the following error is reported:

ERROR: Error fetching repository: java.io.IOException: Expected directory at <SDK>/ndk-bundle/platforms
but it is not a directory or it does not exist. Unable to read the Android NDK at <SDK>/ndk-bundle, the path
may be invalid. Is the path in android_ndk_repository() or ANDROID_NDK_HOME set correctly? If the path is
correct, the contents in the Android NDK directory may have been modified.

The error is barely surprising, considering:

The deprecated <NDK>/platforms and <NDK>/sysroot directories have been
removed. These directories were merged and relocated into the toolchain during
r19. The location of these contents should not be relevant to anyone,
including build systems, since the toolchain handles them implicitly. If you
are using a build system that hasn't adapted to the changes introduced in NDK
r19, file a bug with your build system maintainer. See the [Build System
Maintainers Guide] for information on using the NDK in your own build system.

Can somebody kindly address this? Right now the NDK support appears to be broken outright.

@ahumesky
Copy link
Contributor

This looks like the same issue as #12889. Does android_ndk_repository still work for r21 for you?

@ahumesky ahumesky added P2 We'll consider working on this in future. (Assignee optional) type: feature request and removed untriaged labels Jun 18, 2021
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label May 10, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Android Issues for Android team type: feature request
Projects
None yet
Development

No branches or pull requests

3 participants