-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
new_local_repository does not respect 'includes' attribute #66
Comments
that was supposed to be include jni.h with angle brackets. |
Not sure I agree using the example above: bazel build //external:jni ERROR: /private/var/tmp/bazel_pbethe/d03eb8f816153c36c4229eeab3f690b4/.external-repository/jni-local/BUILD:12:12: error globbing [*/_.h]: /private/var/tmp/_bazel_pbethe/d03eb8f816153c36c4229eeab3f690b4/.external-repository/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/external/jni-local/darwin (Too many levels of symbolic links). |
I think this can be worked around with more judicious globbing until #87 is fixed. |
Running with --nobatch then --batch ensures the second run kills the first one (because of changed startup flags) and the second one too (because of --batch). The `kill` assertions in lines bazelbuild#66 and bazelbuild#67 now succeed. Change-Id: Ibee4997783a820858fc2d2bdda02082a91385d0e
suppose you want to link against the system jni headers on a Mac that might be a WORKSPACE entry of:
When you try and compile a file which has
#include <jni.h>
:The text was updated successfully, but these errors were encountered: