-
Notifications
You must be signed in to change notification settings - Fork 4k
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
cquery --output=files is not useful for external dependencies #17658
Comments
There are pros and cons to emitting relative paths: They are hermetic (don't differ between developer machines), but at the same slightly harder to use (require prefixing with @jscheid-ventana What do you think, would prominently documenting the fact that the paths emitted by |
Yes. Documentation would help clarify context for usage of output (versus some assumption that the |
Fixes bazelbuild#17658 Closes bazelbuild#17721. PiperOrigin-RevId: 517408960 Change-Id: I5a9a0ed82d457511796ee9f538ac86270fc4c16f
Description of the feature request:
With #15979
cquery --output=files
provides a relative path to the output or source file. The feature request is to make the output as readily usable when the target is from an external dependency.Bazel 6.0.0
There is no WORKSPACE-relative "external" directory.
I happen to know that I can currently use
$(bazel info output_path)/..
to get the parent directory to "external", but that's arcane knowledge and isn't directly provided by the cquery feature.What underlying problem are you trying to solve with this feature?
Have
cquery --output=files
behave consistently for all files known to bazel.Which operating system are you running Bazel on?
Linux
What is the output of
bazel info release
?release 6.0.0
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Have you found anything relevant by searching the web?
Linked issues and PRs associated with #15979
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: