Really simple example: Project structure: [image] build.zig: const std = @import("std"); pub fn build(b: *std.Build) void { const target = b.standardTargetOptions(.{}); const optimize = b.standardOptimizeOption(.{}); const exe_mod = b.createModule(.{ .root_source_file = b.…

@embedFile takes a path relative to the current file, or an absolute path, or the name of an import. Adding the file to the imports list won’t do anything, you’d have to @import it which will give a compile error since it’s not a zig file. As @cryptocode said, mod.addEmbedPath is for c compilation …

build-system

Sze March 26, 2026, 9:48am 7

Capturing build options in a string Help

You also can use @embedFile if you want to embed the source code of the (generated) config module: const std = @import("std"); const config = @import("config"); const config_string = @embedFile("config"); pub fn main() !void { inline for (comptime std.meta.declarations(config)) |decl| { std.debug.print("{s: <10}{any}\n", .{ decl.name ++ ":", @field(config, decl.name) }); } std.debug.print("\nor the config source:\n{s}", .{config_string}); } Options are just implemented a…

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled

Embedding files using build.zig