Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken on newer zig versions (not sure since when) #51

Closed
sudokit opened this issue Aug 4, 2023 · 1 comment
Closed

Broken on newer zig versions (not sure since when) #51

sudokit opened this issue Aug 4, 2023 · 1 comment

Comments

@sudokit
Copy link

sudokit commented Aug 4, 2023

At somepoint they changed something that now you cant just pass a string, you need to pass a
"LazyPath". Something like:

b.someFunc(.{.path="/file/path"});

and some other changes too.

user@user-NC-A315-51-56HD ~/D/d/zgui (main)> zig build run
/home/user/Documents/dev/zgui/.zigmod/deps/git/github.com/capy-ui/capy/build_capy.zig:147:54: error: expected type 'Build.LazyPath', found '*const [102:0]u8'
                .x86_64 => step.addObjectFile(prefix ++ "/src/backends/win32/res/x86_64.o"),
                                              ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/home/user/.local/bin/zig-linux-x86_64-0.12.0-dev.1+a327d8b99/lib/std/Build.zig:1672:22: note: union declared here
pub const LazyPath = union(enum) {
                     ^~~~~
/home/user/.local/bin/zig-linux-x86_64-0.12.0-dev.1+a327d8b99/lib/std/Build/Step/Compile.zig:1013:46: note: parameter type declared here
pub fn addObjectFile(self: *Compile, source: LazyPath) void {
                                             ^~~~~~~~
referenced by:
    build: /home/user/Documents/dev/zgui/build.zig:23:42
    runBuild__anon_7154: /home/user/.local/bin/zig-linux-x86_64-0.12.0-dev.1+a327d8b99/lib/std/Build.zig:1639:37
    remaining reference traces hidden; use '-freference-trace' to see all reference traces

Not really sure.

Tried on 0.12.0-dev.1+a327d8b99 and zig-0.11.0-dev.4408+9e19969e0

@zenith391
Copy link
Member

Fixed by #54

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants