Build fails

[larkinxp]

Couldn't post an issue. New to zig so I'm not sure if this is an issue any way. I cloned the repository and try to build with zig 0.15.1 and it fails. I installed all of the dependencies in the README. Linux/WSL Ubuntu 25.04.

user@DESKTOP-LK89LR1:/d/projects/zig/nodb-explorer/libs/libqt6zig$ zig build -Denable-workaround
thread 872707 panic: reached unreachable code
/home/user/.zig/lib/std/debug.zig:559:14: 0x10b0179 in assert (std.zig)
    if (!ok) unreachable; // assertion failure
             ^
/home/user/.zig/lib/std/hash_map.zig:873:19: 0x14e2273 in putAssumeCapacityNoClobberContext (std.zig)
            assert(!self.containsContext(key, ctx));
                  ^
/home/user/.zig/lib/std/hash_map.zig:1449:58: 0x149b57b in grow (std.zig)
                    map.putAssumeCapacityNoClobberContext(k, v, ctx);
                                                         ^
/home/user/.zig/lib/std/hash_map.zig:1296:30: 0x1420cc7 in growIfNeeded (std.zig)
                try self.grow(allocator, capacityForSize(self.load() + new_count), ctx);
                             ^
/home/user/.zig/lib/std/hash_map.zig:1115:34: 0x13a2c2b in getOrPutContextAdapted__anon_79959 (std.zig)
                self.growIfNeeded(allocator, 1, ctx) catch |err| {
                                 ^
/home/user/.zig/lib/std/hash_map.zig:1100:56: 0x12e4045 in getOrPutContext (std.zig)
            const gop = try self.getOrPutContextAdapted(allocator, key, ctx, ctx);
                                                       ^
/home/user/.zig/lib/std/hash_map.zig:1026:52: 0x127ecbe in putContext (std.zig)
            const result = try self.getOrPutContext(allocator, key, ctx);
                                                   ^
/home/user/.zig/lib/std/hash_map.zig:1023:35: 0x122a9e4 in put (std.zig)
            return self.putContext(allocator, key, value, undefined);
                                  ^
/d/projects/zig/nodb-explorer/libs/libqt6zig/build.zig:95:47: 0x11e4dc0 in build (build.zig)
                        try prefix_options.put(allocator, name, map_value);
                                              ^
/home/user/.zig/lib/std/Build.zig:2215:44: 0x11f9bfa in runBuild__anon_23539 (std.zig)
        .error_union => try build_zig.build(b),
                                           ^
/home/user/.zig/lib/compiler/build_runner.zig:366:29: 0x11c3fd1 in main (build_runner.zig)
        try builder.runBuild(root);
                            ^
/home/user/.zig/lib/std/start.zig:627:37: 0x11cac49 in posixCallMainAndExit (std.zig)
            const result = root.main() catch |err| {
                                    ^
/home/user/.zig/lib/std/start.zig:232:5: 0x11a9331 in _start (std.zig)
    asm volatile (switch (native_arch) {
    ^
???:?:?: 0x0 in ??? (???)
error: the following build command crashed:
.zig-cache/o/1ad412503942941f14d38708fb583311/build /home/user/.zig/zig /home/user/.zig/lib /d/projects/zig/nodb-explorer/libs/libqt6zig .zig-cache /home/user/.cache/zig --seed 0x14e65649 -Zed0da05c67f48116 -Denable-workaround

[rcalixte]

Hi! Thanks for the interest!

The README as of now has a badge near the top of it that states that 0.14.x is supported and that remains true. I tested with a dev build of Zig 0.15.x and the library built successfully (and the examples did not) but I hadn't yet tried with the released version of 0.15. For now, I would be curious to know if it worked on 0.14.1 for you. WSL is not explicitly supported but Windows support is still at a minimum a few weeks away. I hope to have that addressed sooner than later. As for 0.15, there are some other things I also want to address, not just adding proper support. I could see the timeline for those changes some time this week if things work out well. Sorry I don't have a more precise timeline than that if 0.15 support is a major issue for you.

[larkinxp]

Looks like the same error with 0.14.1. Although I'm a bit surprised that it does seem like it could be a WSL issue now. I have all the system libraries installed and it should compile. Also WSL has GUI support so that shouldn't be an issue either but it should at least compile.

user@DESKTOP-LK89LR1:/d/projects/zig/nodb-explorer$ ~/.zig/zig-0.14.1/zig build run
thread 928256 panic: reached unreachable code
/home/user/.zig/zig-0.14.1/lib/std/debug.zig:550:14: 0x1400e7d in assert (build)
    if (!ok) unreachable; // assertion failure
             ^
/home/user/.zig/zig-0.14.1/lib/std/hash_map.zig:872:19: 0x16fd321 in putAssumeCapacityNoClobberContext (build)
            assert(!self.containsContext(key, ctx));
                  ^
/home/user/.zig/zig-0.14.1/lib/std/hash_map.zig:1448:58: 0x16e0d25 in grow (build)
                    map.putAssumeCapacityNoClobberContext(k, v, ctx);
                                                         ^
/home/user/.zig/zig-0.14.1/lib/std/hash_map.zig:1295:30: 0x16be50a in growIfNeeded (build)
                try self.grow(allocator, capacityForSize(self.load() + new_count), ctx);
                             ^
/home/user/.zig/zig-0.14.1/lib/std/hash_map.zig:1114:34: 0x1693339 in getOrPutContextAdapted__anon_114137 (build)
                self.growIfNeeded(allocator, 1, ctx) catch |err| {
                                 ^
/home/user/.zig/zig-0.14.1/lib/std/hash_map.zig:1099:56: 0x164b58d in getOrPutContext (build)
            const gop = try self.getOrPutContextAdapted(allocator, key, ctx, ctx);
                                                       ^
/home/user/.zig/zig-0.14.1/lib/std/hash_map.zig:1025:52: 0x15ffc6e in putContext (build)
            const result = try self.getOrPutContext(allocator, key, ctx);
                                                   ^
/home/user/.zig/zig-0.14.1/lib/std/hash_map.zig:1022:35: 0x15ad942 in put (build)
            return self.putContext(allocator, key, value, undefined);
                                  ^
/home/user/.cache/zig/p/libqt6zig-6.8.2-OSXtXGSatAvmoneMEV-WIp6emTbCTklN0Vpci62Tk3qg/build.zig:95:47: 0x159ed72 in build (build)
                        try prefix_options.put(allocator, name, map_value);
                                              ^
/home/user/.zig/zig-0.14.1/lib/std/Build.zig:2428:44: 0x154da84 in runBuild__anon_75966 (build)
        .error_union => try build_zig.build(b),
                                           ^
/home/user/.zig/zig-0.14.1/lib/std/Build.zig:2408:29: 0x14ff18c in dependencyInner__anon_68601 (build)
        sub_builder.runBuild(bz) catch @panic("unhandled error");
                            ^
/home/user/.zig/zig-0.14.1/lib/std/Build.zig:2230:35: 0x14d8ec4 in dependency__anon_65036 (build)
            return dependencyInner(b, name, pkg.build_root, if (@hasDecl(pkg, "build_zig")) pkg.build_zig else null, pkg_hash, pkg.deps, args);
                                  ^
/d/projects/zig/nodb-explorer/build.zig:158:32: 0x14be183 in build (build)
    const qt6zig = b.dependency("libqt6zig", .{
                               ^
/home/user/.zig/zig-0.14.1/lib/std/Build.zig:2427:33: 0x14aee60 in runBuild__anon_24711 (build)
        .void => build_zig.build(b),
                                ^
/home/user/.zig/zig-0.14.1/lib/compiler/build_runner.zig:339:29: 0x14a7a40 in main (build)
        try builder.runBuild(root);
                            ^
/home/user/.zig/zig-0.14.1/lib/std/start.zig:660:37: 0x14960fa in posixCallMainAndExit (build)
            const result = root.main() catch |err| {
                                    ^
/home/user/.zig/zig-0.14.1/lib/std/start.zig:271:5: 0x1495cad in _start (build)
    asm volatile (switch (native_arch) {
    ^
???:?:?: 0x0 in ??? (???)
error: the following build command crashed:
/d/projects/zig/nodb-explorer/.zig-cache/o/c46763ca214d83f98abbd269c9d1ef17/build /home/user/.zig/zig-0.14.1/zig /home/user/.zig/zig-0.14.1/lib /d/projects/zig/nodb-explorer /d/projects/zig/nodb-explorer/.zig-cache /home/user/.cache/zig --seed 0x88c178a9 -Z1b4eb1862c6be656 run

[rcalixte]

$ ~/.zig/zig-0.14.1/zig build run

It should just be zig build and then whatever options you want to pass in. Also, you should clone and try to build the examples unless you are planning on doing some development on the library itself. The examples are a decent starting point until there's a dedicated application available that should serve as a better example. As of now, the examples are essentially two dozen independent applications in a single repository so the build system isn't as clear as it would be for a single application.

[larkinxp]

I have different versions of zig installed. I just wanted to try it with 0.14.1 as suggested to see if it would build. As far as I know, it should work exactly as on version 0.14.1 just using a different zig binary to build it unless I'm wrong.

[rcalixte]

I have different versions of zig installed. I just wanted to try it with 0.14.1 as suggested to see if it would build. As far as I know, it should work exactly as on version 0.14.1 just using a different zig binary to build it unless I'm wrong.

I see, but you're using zig build run on the library? I'll link the introductory post. Unless you are planning on developing the library itself, you would be best served to start with the examples, assuming all of the dependencies are correctly installed.

On the library, I get this when I try zig build run (which is correct):

$ zig build run
no step named 'run'
  access the help menu with 'zig build -h'

If you're getting a bunch of errors instead of that output, there might be something with your Zig installation worth revisiting.