Currently in a project where I try to link SDL to a *Compile provided by zig's new package manager. I get bogus errors like:
error: unable to check cache: stat file 'D:\a\turbo\turbo\zig-cache\C:\Users\runneradmin\AppData\Local\zig\p\1220dbf1d809d07d1910b9853f162458ed1ebc66be81b21ccfc40a2552bc1019f9c2\.build_config\SDL2\lib\libSDL2.dll.a' failed: FileNotFound
As far as I'm aware, the file paths listed in sdl.json (from .build_config\) could very well be absolute and even if they're not (in my case), they don't seem to be that accessible to executables that exist in zig's cache as opposed to the build root.
By using .cwd_relative instead of .path when working with sdk_paths SDL.zig can link to artifacts from the package manager.
Currently in a project where I try to link SDL to a
*Compileprovided by zig's new package manager. I get bogus errors like:As far as I'm aware, the file paths listed in
sdl.json(from.build_config\) could very well be absolute and even if they're not (in my case), they don't seem to be that accessible to executables that exist in zig's cache as opposed to the build root.By using
.cwd_relativeinstead of.pathwhen working withsdk_pathsSDL.zig can link to artifacts from the package manager.