Intermediate build results (phase A and B) about please HOT 6 OPEN

If I understand correctly, I think you could handle this by selecting tool-C differently based on the architecture:

if CONFIG.OS == 'darwin':
    filegroup(
        name = "tool-C",
        srcs = ["tool-C-bin"],
    )
else:
    go_binary(  # or whatever
        name = "tool-C",
        ....
    )

from please.

This does mean that tool-C-bin has to be put inside the tool-C folder as a file output. And it can not be consumed by transferring the plz-out/gen/tool-C folder to Phase B. Correct?

from please.

If it would be possible to use the cached results on the MacOS machine in Phase B that would be even better in our setup. But when I try to run tool-D on MacOS with the build using tool-C dependencies it would have different hash key because of different build config like the OS variable. So it become unusable.

I would rather keep it as one chain. Because actually we have Phase C too where results are combined again with dependencies from Phase A and B.

from please.

I'm a little confused so forgive me if I've misunderstood. If you need to build a tool on linux and then use it on a macos box, then if you're using something like github actions you could do the following:

Set up a config option for the tool. This can be done in your .plzconfig like so:

    [buildconfig]
    my-tool = //tools:linux_tool

and then use this in your build rules like so:

genrule(
    ...,
    tools = [CONFIG.MY_TOOL],
)

Then you can:

1. build the tool on linux
2. save this as an artefact to your ci build e.g. to /tmp/workspace/my-tool
3. set a .plzconfig.macos_ci (or use -o buildenv.mytool:/tmp/workspace/my-tool) that configures the tool path
4. do your macos build

.plzconfig.macos_ci might look like:

    [buildconfig]
    my-tool = /tmp/workspace/my-tool

from please.

That is a great way indeed. I had not thought of that. Currently I use rules that uses the link label to output it to the folder of the package. Something like this will be found in tool-A and tool-B on the build rule.

labels = ["link:" + package_name() ]

Then I use an additional rule in tool-A and tool-B that uses that output path as a source.
And tool-C can use those rules as its source on the other machine.

But one thing that I was not able to do is to use the data that is already in cache. I need to copy it over in the workspace either way.

from please.