You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Windows Dev Kit: ability for it to upgrade itselfΒ #7392
ok so the unsolved problem with the dev kit is that every time we update the compiler in certain ways, you have to refresh the dev kit in order to keep it working. I have some ideas on how to improve this, but for now the solution is that I need to upload a new dev kit .zip file.
It solves this particular problem, but I'm going to keep the issue open to track the fact that we don't have a way to update the dev kit using the dev kit.
changed the title [-]error: container 'std.macho' has no member called 'EXPORT_SYMBOL_FLAGS_KIND_REGULAR'[/-][+]Windows Dev Kit: ability for it to upgrade itself[/+]on Dec 11, 2020
One workaround for now is to additionally pass --override-lib-dir path\to\zig checkout\lib (e.g. --override-lib-dir C:\Users\Evan\projects\zig\lib) when using the compiler kit. This will work if trying to compile Zig when it uses new standard library features. It may not help if the compiler or build tools change in other ways though.
I confirmed that this workaround allows compiler kit 8076894d8 to build latest master 6ab5beb (without the additional flag it breaks due to missing std.fs.path.extension
Activity
andrewrk commentedon Dec 11, 2020
ok so the unsolved problem with the dev kit is that every time we update the compiler in certain ways, you have to refresh the dev kit in order to keep it working. I have some ideas on how to improve this, but for now the solution is that I need to upload a new dev kit .zip file.
andrewrk commentedon Dec 11, 2020
FYI the dev kit link is updated: https://github.com/ziglang/zig/wiki/Building-Zig-on-Windows
It solves this particular problem, but I'm going to keep the issue open to track the fact that we don't have a way to update the dev kit using the dev kit.
[-]error: container 'std.macho' has no member called 'EXPORT_SYMBOL_FLAGS_KIND_REGULAR'[/-][+]Windows Dev Kit: ability for it to upgrade itself[/+]ehaas commentedon Dec 12, 2020
One workaround for now is to additionally pass
--override-lib-dir path\to\zig checkout\lib(e.g.--override-lib-dir C:\Users\Evan\projects\zig\lib) when using the compiler kit. This will work if trying to compile Zig when it uses new standard library features. It may not help if the compiler or build tools change in other ways though.I confirmed that this workaround allows compiler kit
8076894d8to build latest master 6ab5beb (without the additional flag it breaks due to missingstd.fs.path.extensionandrewrk commentedon Dec 12, 2020
I updated the wiki instructions to suggest the
--override-lib-dirtip.