It's hard to refer to target-framework-specific output from our targets. We should use either OutputGroup providers or pre-declared outputs (maybe both?) to make this easier.
We use the outputs from the first listed target framework to populate DefaultInfo. The idea there was to make bazel run/bazel test only build a small amount of stuff.
That being said, we probably want it to be easy, via the CLI and via labels, to get the other frameworks. Predeclared outputs look like they'd give us labels, OutputGroups look like they'd be handy for the CLI.
https://docs.bazel.build/versions/master/skylark/rules.html#requesting-output-files
It's hard to refer to target-framework-specific output from our targets. We should use either
OutputGroupproviders or pre-declared outputs (maybe both?) to make this easier.We use the outputs from the first listed target framework to populate
DefaultInfo. The idea there was to makebazel run/bazel testonly build a small amount of stuff.That being said, we probably want it to be easy, via the CLI and via labels, to get the other frameworks. Predeclared outputs look like they'd give us labels,
OutputGroups look like they'd be handy for the CLI.This requires a bit of investigation still.