How to set std_options in zigar?

[MichaelBelousov]

I have the following code in my zigar entry zig file:

pub const std_options: std.Options = .{
    .log_level = .info,
};

In a normal zig compilation, this should override the log_level to always be .info, otherwise it's .err in the release builds. Because std.zig in the zig std defines it to:

/// Stdlib-wide options that can be overridden by the root file.
pub const options: Options = if (@hasDecl(root, "std_options")) root.std_options else .{};

But the behavior continues to be that of me not having defined an std_options in the root module. I assume zigar is using its own root for setup, and then importing the entry file somewhere there. Can the new root inherit std_options? (and maybe other things I'm unaware of that depend on the root module)

[chung-leong]

Good catch. It's not something I considered. stub-napi.zig or stub-wasm.zig in zigar-compiler/zig serve as the root. They should expose std_options from the module if it's present. I've opened an issue.