Updated to zig 0.15.1

[Logickin-Lambda]

The commit addresses the outdated zig version used in the library. While most of the code can use the same treatment by updating callconv(.c) and the build structure of build.zig; there are two changes might require follow up though:

As discussed in this issue, we can directly remove the usingnamespace keyword surrounding the function, but since emscripten_sleep(1) is exclusive for emscripten build, I ended up conditionally build the function by checking if the target platform is emscripten; otherwise, it will be an empty function.

var wgpuDeviceTickWarnPrinted: bool = false;

pub fn wgpuDeviceTick() void {
    if (emscripten) {
        if (!wgpuDeviceTickWarnPrinted) {
            std.log.warn("wgpuDeviceTick(): this fn should be avoided! RequestAnimationFrame() is advised for smooth rendering in browser.", .{});
            wgpuDeviceTickWarnPrinted = true;
        }
        emscripten_sleep(1);
    }
}

Since I don't have any emscripten project on hands, I might need others to confirm if this implementation works.

Another change is the use of std.BoundedBuffer which is also deprecated in the 0.15.1, and suggested by the release notes, the substitution is to use ArrayListUnmanaged which will also be removed in the future version; thus, I have to use ArrayList, but because ArrayList requires an allocator for appending items, i ended up choosing fixedBufferAllocator like shown:

// TODO: We support up to 32 command buffers for now. Make it more robust.
var buffer: [32]wgpu.CommandBuffer = undefined;
var fb_allocator = std.heap.FixedBufferAllocator.init(@ptrCast(&buffer));

var command_buffers = std.ArrayList(wgpu.CommandBuffer).initCapacity(fb_allocator.allocator(), 32) catch unreachable;
command_buffers.append(fb_allocator.allocator(), stage_commands) catch unreachable;
command_buffers.appendSlice(fb_allocator.allocator(), commands) catch unreachable;

However, although this solution works and I have successfully to replicate the triangle example from the zig-gamedev with the updated library, the current solution doesn't address the TODO item.

[Logickin-Lambda]

Hmmm... I think I need some help this time, mainly about not familiar with ELF file, and I primary worked on windows. Tried to build the project with linux, and the same error pops up, but there is not much information about where it causes the issue.

[Erdragh]

I'm new to zig, but I can at least get it to get through zig build when I change zdawn to be linked dynamically:

zgpu.patch

[Logickin-Lambda]

Thanks, added linkage to dynamic, it seems worked without the compile error. Tried to build the project from my testing triangle shader program, and it still works without any issues.

Edit: the change has been committed, and let's see if this is a valid fix.

[Copilot]

Pull Request Overview

This PR updates the zgpu library from Zig 0.14.0 to 0.15.1, addressing breaking changes in the language and standard library. The update primarily involves:

• Updating calling convention syntax from .C to .c
• Replacing deprecated std.BoundedArray with std.ArrayList using a FixedBufferAllocator
• Refactoring the wgpuDeviceTick function to use conditional compilation instead of usingnamespace

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/zgpu.zig	Updated calling conventions, replaced BoundedArray with ArrayList using FixedBufferAllocator, refactored emscripten-specific code to use conditional compilation
src/wgpu.zig	Updated calling conventions in callback type definitions
build.zig.zon	Updated minimum Zig version requirement to 0.15.1
build.zig	Added dynamic linkage configuration for zdawn library

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] The buffer is left uninitialized (undefined). While this works with FixedBufferAllocator, it's better practice to initialize it with .{} for clarity and to avoid potential issues with future Zig versions that may have stricter safety checks.

Suggested change

	var buffer: [32]wgpu.CommandBuffer = undefined;
	var buffer: [32]wgpu.CommandBuffer = .{};

[hazeycode]

Looks like the linkage change doesn't sit well on macOS. I guess want to avoid dynamically linking anyway. Otherwise changes look good

[Logickin-Lambda]

Looks like the linkage change doesn't sit well on macOS. I guess want to avoid dynamically linking anyway. Otherwise changes look good

Thank you! So my concern to the dynamic linking was right, and we definitely need to get rid of it in some sort. According to the fork from @tristanpemble, could the use of llvm be the fix?

Unfortunately, this might not be something I could fixed on my end because I don't have a Mac and well enough understanding to linux. Since I have seen some people forked my version recently, I wish to see if anyone could help or share some ideas on the mac and the linux side of the library.

[hazeycode]

Yes I think we should set to use llvm here. I can test on mac and Linux.

[Logickin-Lambda]

Cool, with the llvm used, all three tests are now passed.

[hazeycode]

Thanks!