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

Bazel fails recognizing current workspace name when building remote repositories #1312

Closed
katzdm opened this issue May 25, 2016 · 1 comment

Comments

@katzdm
Copy link

katzdm commented May 25, 2016

If a workspace "SomeLib" includes a git_repository-rule, referencing an external repository which itself remotely references "@SomeLib//"-targets, Bazel will fail to find "SomeLib" during building of build-targets in the external repository, giving a "no such package" error. Bazel should recognize that the "SomeLib"-repository referenced in the external repository is the same as the current workspace, and build accordingly. This probably amounts to including a symlink in the "external/" directory for the current workspace.

@kchodorow
Copy link
Contributor

Duplicate of #1248.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants