Declare a target as unsupported in build.zig

[tensorush]

I’ve had a similar issue when trying to run scoop’s doc and fmt steps on Linux CI/CD runners.

I solved it by returning either a public Darwin or a private Linux module from an if/else block:

scoop/build.zig at main

If you’d still like to let Linux users know that their OS isn’t supported you can std.log.err your message.

In general, when it comes to handling failing cases you shouldn’t reach for errors, but rather consider using either b.addFail, std.log.err, or @panic/std.debug.panic.

UPD: I’ve added failing case handling to the Doc:

Build System Tricks

This community-driven doc is an attempt to expand on the official Zig Build System documentation as well as the past community contributions by xq, Sobeston and others. Here you’ll find a list of tricks on how to use every part of the build system while making sure to conveniently name and lay out your build steps. I. Basic Usage 1) Declare commonly used information upfront // Resolve a query for a custom target const my_target = b.resolveTargetQuery(.{ .cpu_arch = .wasm32, .os_tag =…