use case: have a way for zon to define which `--build-file` to use

[nektro]

this option is available to zig build when you want to run a build in a file other than build.zig. it should be available to consumers of packages as well.

[andrewrk]

can you elaborate more on this use case?

[nektro]

for instance if a package provided a module in build.foo.zig so as to not interfere with an incompatible root build.zig then users might be able to pass .build_file = "build.foo.zig", in their zon file to obtain access to the module

there's also been various talks about support for "monorepos" and they could also be supported through this with .build_file = "foo/build.zig",

[andrewrk]

I think this needs a full example to remain open. It's difficult to understand based on this description alone.

[nektro]

https://gist.github.com/nektro/a28d4aadca050d32ab8ea5723bcb6739

the expected output of cloning this and running zig build run is:

info: 184
info: 486

[nektro]

another better alternative to the exact code i provided is if .build_file = "build.zig.zig", could be read from the zon of the package being depended on, rather than having to be a field on the consumer