Q. When there are resource files for different archtiectures (e.g., prebuilt binaries for x86-64 and aarch64), is there any way to include them selectively when building packages for a specific platform?

Hi, there is not currently via BUILD files, but it possible with plugins. This is how downloading tools like

Protoc

works I think it'd be cool if we supported this via BUILD files. I'm not sure what an ideal design would look like. Any thoughts? -- In the meantime, are you blocked? We can help w/ writing a little plugin

If I could run a specific shell script before/after specific build targets, this could be side-stepped in that way, but I think pants won't be happy with arbitrarily removed files, etc.

If I could run a specific shell script before/after specific build targets

Have you seen this page? https://www.pantsbuild.org/docs/run-shell-commands

um, the link says 404 not found

fixed

but i'm aware of the experimental shell commands

would there be any possibility to hook into the MANIFEST (or something like package-data section) generation steps of the setup-py generator?

How is that working? Generally, you would likely create a new target type, maybe like this:

platform_specific_resource(
   linux_x86_source="linux.ext",
   macos_x86_source="mac.ext",
)

Then, you will use "codegen". It looks similar to https://github.com/pantsbuild/pants/blob/main/src/python/pants/backend/docker/util_rules/dockerfile.py, where you create a

GenerateSourcesRequest

. But it would be

input=MyCustomSourceField

and

output=ResourceSourceField

. You'll request the type

Platform

in the rule and figure out which file to load based on that

or, could i define my own

platform_specific_resources()

target which resembles the vanilla

resources()

target? (where I can control the target platform using a CLI argument or environment variable)

Where I can control the target platform using a CLI argument or environment variable

You could do that too if you want. For CLI arguments, you would set up a subsystem and then consume it in your rule https://www.pantsbuild.org/docs/rules-api-subsystems For env variable, https://www.pantsbuild.org/docs/rules-api-process#environment-variables

ok, I'll look into you references