diff options
| author | 2021-01-23 19:09:01 +0100 | |
|---|---|---|
| committer | 2021-01-24 01:23:09 +0100 | |
| commit | 2a51619a12350c21689c32086c3482fb9815e260 (patch) | |
| tree | 6eb0f93a24f1393e87fdf02823a62ad3a5c45885 /build.zig | |
| parent | rework of the test database initialization (diff) | |
| download | zig-sqlite-2a51619a12350c21689c32086c3482fb9815e260.tar.gz zig-sqlite-2a51619a12350c21689c32086c3482fb9815e260.tar.xz zig-sqlite-2a51619a12350c21689c32086c3482fb9815e260.zip | |
build: default to in-memory tests
Now that we use `std.testing.tmpDir` we're actually hitting the disk,
which made me realize that the tests run significantly slower than
before, because on my system `/tmp` is a tmpfs which is already in
memory.
Diffstat (limited to 'build.zig')
| -rw-r--r-- | build.zig | 4 |
1 files changed, 2 insertions, 2 deletions
| @@ -16,8 +16,8 @@ pub fn build(b: *std.build.Builder) void { | |||
| 16 | const target = b.standardTargetOptions(.{}); | 16 | const target = b.standardTargetOptions(.{}); |
| 17 | const mode = b.standardReleaseOptions(); | 17 | const mode = b.standardReleaseOptions(); |
| 18 | 18 | ||
| 19 | const in_memory = b.option(bool, "in_memory", "Should the tests run with sqlite in memory") orelse false; | 19 | const in_memory = b.option(bool, "in_memory", "Should the tests run with sqlite in memory (default true)") orelse true; |
| 20 | const use_bundled = b.option(bool, "use_bundled", "Use the bundled sqlite3 source instead of linking the system library") orelse false; | 20 | const use_bundled = b.option(bool, "use_bundled", "Use the bundled sqlite3 source instead of linking the system library (default false)") orelse false; |
| 21 | 21 | ||
| 22 | // Build sqlite from source if asked | 22 | // Build sqlite from source if asked |
| 23 | if (use_bundled) { | 23 | if (use_bundled) { |