-
Notifications
You must be signed in to change notification settings - Fork 263
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
r11b: ndk-which dosen't work #29
Milestone
Comments
Windows is WAI. It's a shell script, and has never had a Windows implementation. We could leave this open as a feature request to add such a script. As for being broken on Linux/Mac... oops. Since the implementation script lives in the different directory, a path needs to be updated. L30 should be: -MYNDKDIR=`dirname $0`
+MYNDKDIR=`dirname $0`/../../.. Will get a fix out for that in r12. |
Thanks. MYNDKDIR fix worked for me. |
DanAlbert
added a commit
that referenced
this issue
Apr 16, 2016
We moved the installed location of `ndk-which` into prebuilts/blah. Update the path from there to the root. Fixes #29. Change-Id: I9d36a3862e438ad517f2a4f8070b211548f602d4
Closed
This was referenced May 22, 2023
[BUG] build error: clang frontend command failed with exit code 139 (use -v to see invocation)
#1889
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Windows x64
I tried rename "ndk-which" to "ndk-which.cmd"
Linux / Mac
The text was updated successfully, but these errors were encountered: