aboutsummaryrefslogtreecommitdiff
path: root/lib/std/Build.zig
diff options
context:
space:
mode:
authormlugg <mlugg@mlugg.co.uk>2025-04-20 17:54:11 +0100
committerMatthew Lugg <mlugg@mlugg.co.uk>2025-04-22 22:50:36 +0100
commit927f233ff82bd422b387b4eef7fcbc67823e4b85 (patch)
treeb921686a62e6e60efa6db973488d9fffb93c8ebb /lib/std/Build.zig
parent6a7ca4b8b0fcce9e5f6a4d3f799e83021929c975 (diff)
downloadzig-927f233ff82bd422b387b4eef7fcbc67823e4b85.tar.gz
zig-927f233ff82bd422b387b4eef7fcbc67823e4b85.zip
compiler: allow emitting tests to an object file
This is fairly straightforward; the actual compiler changes are limited to the CLI, since `Compilation` already supports this combination. A new `std.Build` API is introduced to allow representing this. By passing the `emit_object` option to `std.Build.addTest`, you get a `Step.Compile` which emits an object file; you can then use that as you would any other object, such as either installing it for external use, or linking it into another step. A standalone test is added to cover the build system API. It builds a test into an object, and links it into a final executable, which it then runs. Using this build system mechanism prevents the build system from noticing that you're running a `zig test`, so the build runner and test runner do not communicate over stdio. However, that's okay, because the real-world use cases for this feature don't want to do that anyway! Resolves: #23374
Diffstat (limited to 'lib/std/Build.zig')
-rw-r--r--lib/std/Build.zig6
1 files changed, 5 insertions, 1 deletions
diff --git a/lib/std/Build.zig b/lib/std/Build.zig
index d31d9f3ee0..8ce4fe40e3 100644
--- a/lib/std/Build.zig
+++ b/lib/std/Build.zig
@@ -1019,6 +1019,10 @@ pub const TestOptions = struct {
use_llvm: ?bool = null,
use_lld: ?bool = null,
zig_lib_dir: ?LazyPath = null,
+ /// Emits an object file instead of a test binary.
+ /// The object must be linked separately.
+ /// Usually used in conjunction with a custom `test_runner`.
+ emit_object: bool = false,
/// Prefer populating this field (using e.g. `createModule`) instead of populating
/// the following fields (`root_source_file` etc). In a future release, those fields
@@ -1067,7 +1071,7 @@ pub fn addTest(b: *Build, options: TestOptions) *Step.Compile {
}
return .create(b, .{
.name = options.name,
- .kind = .@"test",
+ .kind = if (options.emit_object) .test_obj else .@"test",
.root_module = options.root_module orelse b.createModule(.{
.root_source_file = options.root_source_file orelse @panic("`root_module` and `root_source_file` cannot both be null"),
.target = options.target orelse b.graph.host,