windows zon issue

[kinecology]

On Windows, I had to modify build.zig.zon to get it to download the tars:

        .zigwin32 = .{
            // .url = "https://github.com/kristoff-it/zigwin32/archive/1102e9b82e8bd50913b6a78035bfb399ebd8cf97.tar.gz",
            .url = "https://codeload.github.com/kristoff-it/zigwin32/archive/tar.gz/1102e9b82e8bd50913b6a78035bfb399ebd8cf97",
            .hash = "zigwin32-25.0.28-preview-6BfVhYKN5AOvXPVJq4bGZ7C5dM3PbUra4xhKAKOFJGcF",
            .lazy = true,
        },
        .icons = .{
            // .url = "https://github.com/foxnne/zig-lib-icons/archive/db034786a1286ab28dc35aba534c098aa4f1a3aa.tar.gz",
            .url = "https://codeload.github.com/foxnne/zig-lib-icons/archive/tar.gz/db034786a1286ab28dc35aba534c098aa4f1a3aa",
            .hash = "icons-0.0.0-iJxA-VvGMwAgiKSXRe_Y0O7RpasdtEJhBfVx8IGGEBl_",
            .lazy = true,
        },

just FYI.

[foxnne]

Interesting. I build this on windows frequently without issue, and I haven't seen other repo's forced to use the codeload URLs. I'll try to replicate this on Windows asap

[kinecology]

I'm on Windows 10 still, so you can probably ignore.
BTW, GUI looks great.

[foxnne]

Ah! I don't have a win 10 machine to test... I'd love to still support win 10 somehow (though the titlebar coloring and transparency wont work). I'm now wondering why windows 10 matters for the .zon and downloading packages...

[kinecology]

Not sure why it matters, but it only happened for those two packages, zigwin32 and icons. It could be random, interference from antivirus or something. I'll be upgrading to Win 11 in a few months. Most of my work is in WSL2 so it hasn't been urgent. I just explore zig stuff in Win32.

[ZackeryRSmith]

If I had to guess, this is due to some upstream (or computer) issue, not Fizzy itself. I have tested it on three Windows 10 machines, and I cannot reproduce it, sadly. Using the git+https protocol available since zig 0.12.0 (see #17277) may fix this? At least all of our git-related dependencies should be updated to use it.

Why are we even using an outdated fork of zigwin32 (kristoff-it/zigwin32)? I see now it was due to the lack of 0.16.0 support. This is now fixed. As such we should point directly towards the main repository (marlersoft/zigwin32). Regardless you should write off switching as low priority.