-
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
cc_binary: linkmap support #20966
Comments
Unfortunately Bazel team is very short on C++ rules support, so we can't accept new features ATM. |
That it unfortunate as there is no generic way to make Do you have a very rough estimation on how long "ATM" could be? |
I don't know, I don't have any rough estimates. |
See bazelbuild#20966. ~I'm not entirely sure how to test the unix-only functionality.~ Closes bazelbuild#20967. PiperOrigin-RevId: 616728419 Change-Id: I0b8eaa8245becebe2047bfc2bd7725f3fd45b8f1
Closing, as my PR got merged. |
A fix for this issue has been included in Bazel 7.2.0 RC1. Please test out the release candidate and report any issues as soon as possible. |
Description of the feature request:
Our development process relies on linkmaps for binaries.
Currently
cc_binary
is not able to generate those.While the necessary plumbing exists in
cc_common
withaddition_linker_outputs
this is not exposed as interface viacc_binary
.The
generate_linkmap
feature as used by the objc toolchain could be reused.Which category does this issue belong to?
C++/Objective-C Rules
What underlying problem are you trying to solve with this feature?
Debugging of binaries.
Which operating system are you running Bazel on?
Linux
What is the output of
bazel info release
?release 7.0.1
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?
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: