Add custom additional_outputs to cc_common.link

[lior10r]

Description of the feature request:

We have a custom toolchain that outputs more than one file in the linking action. We would like to access these files later in the build process.
Today we have no way of accessing these files because bazel doesn't declare them as outputs of the linking action.

ideally these additional output files would be taken from a definition in the cc toolchain.

Which category does this issue belong to?

C++ Rules

What underlying problem are you trying to solve with this feature?

Retrieve additional (non-standard) output files from the sandbox when compiling via cc_common.link

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 7.4.1

If bazel info release returns development 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 HEAD ?

Have you found anything relevant by searching the web?

I have found this issue: #22036 which asks for something very similar but for cc_common.compile

Any other information, logs, or outputs that you want to share?

No response

[lior10r]

Is it possible that we would develop this and someone would go over a PR?

[keith]

this parameter already exists

bazel/src/main/starlark/builtins_bzl/common/cc/cc_common.bzl

Line 66 in 37e0d23

additional_outputs = [],

, maybe try that one? it might be marked as private API in which case I would attempt to remove that mark and see if it would already do what you need

[lior10r]

Yes the parameter exists but if you look in here:
cc_binary.bzl
You can see that they only pass predefined files (linkmap and pdb). We would like to add other additional outputs.
I needed to explain this better, after we saw the code we thought about using this parameter but being able to pass to it custom files that the toolchain would define.
It is more correct to say that we would like to add custom outputs to cc_binary