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
deploy_info gobinary visibility breaks builds when defining a custom android toolchain #209
Comments
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Feb 28, 2024
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Mar 4, 2024
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Mar 4, 2024
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Mar 5, 2024
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Mar 5, 2024
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Mar 14, 2024
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Mar 26, 2024
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Apr 19, 2024
Bencodes
added a commit
to Bencodes/rules_android
that referenced
this issue
Apr 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The go binary that was introduced as part of this commit aeb70ea#diff-04ca49b91bef564e399d9f954024ca9562661adc03742a55be6206dddb5fc53bR9 does not have the correct visibility that allows others to define custom toolchains outside
rules_android
.Repro:
The text was updated successfully, but these errors were encountered: