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

//external:android/crosstool depends on @androidndk//:default_crosstool in repository @androidndk which failed to fetch. no such package '@androidndk//': Could not read RELEASE.TXT in Android NDK: /home/nd/Android/Sdk/ndk/RELEASE.TXT (No such file or directory) #98

Closed
JimReno opened this issue Sep 10, 2019 · 5 comments
Assignees
Labels
platform:android Issues with Android as Platform

Comments

@JimReno
Copy link

JimReno commented Sep 10, 2019

I followed the instruction to set up Android Studio with MediaPipe. When I import the build file with bazel, error occured.
图片

I opened the ndk folder but can't find RELEASE.TXT. But I did installed ndk in the Adroid Studio. Please give me some hint about this problem. Thanks anyway. :)

@JimReno JimReno changed the title Error:/home/nd/workspace/zjc/mediapipe/WORKSPACE:241:1: //external:android/crosstool depends on @androidndk//:default_crosstool in repository @androidndk which failed to fetch. no such package '@androidndk//': Could not read RELEASE.TXT in Android NDK: /home/nd/Android/Sdk/ndk/RELEASE.TXT (No such file or directory) //external:android/crosstool depends on @androidndk//:default_crosstool in repository @androidndk which failed to fetch. no such package '@androidndk//': Could not read RELEASE.TXT in Android NDK: /home/nd/Android/Sdk/ndk/RELEASE.TXT (No such file or directory) Sep 10, 2019
@jiuqiant
Copy link
Contributor

jiuqiant commented Sep 10, 2019

Can you report the following system information to help us understand your issue:

  • OS Platform and Distribution (e.g., Linux Ubuntu 16.04)
  • Bazel version
  • Android Studio, NDK, SDK versions (if issue is related to building in mobile dev environment
  • Your environment variables: $ANDROID_HOME and $ANDROID_NDK_HOME

Moreover, do you install NDK by yourself? If it's installed by Android Studio, it's likely to be put into Android/Sdk/ndk-bundle/ instead of Android/Sdk/ndk/. Have you modified the WORKSAPCE file?

@jiuqiant jiuqiant added the stat:awaiting response Waiting for user response label Sep 10, 2019
@JimReno
Copy link
Author

JimReno commented Sep 11, 2019

Thanks for reply. Sure. The system information are listed below:

  • OS Platform and Distribution : Linux Ubuntu 16.04
  • Bazel version:0.29.0
  • Android Studio SDK version: 29 NDK version: 20.0.5594570
  • environment variables: $ANDROID_HOME:/home/nd/Android/Sdk $ANDROID_NDK_HOME:/home/nd/Android/Sdk/ndk.
    图片

I follow the instruction and installed the NDK in Android Studio. And I didn't modified the workspace file.
图片

@jiuqiant jiuqiant added platform:android Issues with Android as Platform and removed stat:awaiting response Waiting for user response labels Sep 11, 2019
@jiuqiant
Copy link
Contributor

I can reproduce this issue with Android Studio 3.5 on Linux now.
The latest Android Studio (3.5) puts the ndk libraries into Android/Sdk/ndk/<version number> instead of Android/Sdk/ndk-bundle/ . For your case, the $ANDROID_NDK_HOME should be /home/nd/Android/Sdk/ndk/20.0.5594570.

We will update install.md soon to mention this change. Thanks.

@jiuqiant jiuqiant self-assigned this Sep 11, 2019
@jiuqiant
Copy link
Contributor

The instruction of setting up MediaPipe with Android Studio is updated. See install.md.

@jiuqiant jiuqiant added the stat:awaiting response Waiting for user response label Sep 12, 2019
@mgyong mgyong closed this as completed Sep 16, 2019
@jiuqiant jiuqiant removed the stat:awaiting response Waiting for user response label Sep 26, 2019
@dizcza
Copy link

dizcza commented Aug 1, 2023

The instruction of setting up MediaPipe with Android Studio is updated. See install.md.

Dead link.

I must note that the official documentation at https://developers.google.com/mediapipe/framework/getting_started/android still does not note the correct way to determine the ANDROID_NDK_HOME. Had I not read this conversation, I wouldn't have known what to do either.

arttupii pushed a commit to arttupii/mediapipe that referenced this issue Nov 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform:android Issues with Android as Platform
Projects
None yet
Development

No branches or pull requests

4 participants