[Windows] Unable to build latest wireguard missing i686-w64-mingw32-windres

[Windows] Unable to build latest wireguard missing i686-w64-mingw32-windres

[Manikandan Thiagarajan]

Hi,

I am trying to update Wireguard to latest version on windows but could
not build because of missing dependencies i686-w64-mingw32-windres.
I can't go back to older commit such as 0.3.4 (a5102ca - version:
bump) because of go mod has reference to unknown revision
76ef01985b1c.
Please suggest how to fix either one of these issues. I can use either
of these commits.

Building off of commit 5f420f6 - manager: pipeline UAPI requests
'i686-w64-mingw32-windres' is not recognized as an internal or external command,
operable program or batch file.
[-] Failed with error #1.

Building off of commit a5102ca - version: bump
[+] Building library x86
get "golang.zx2c4.com/wireguard/windows": found meta tag
get.metaImport{Prefix:"golang.zx2c4.com/wireguard/windows", VCS:"git",
RepoRoot:"https://git.zx2c4.com/wireguard-windows"} at
//golang.zx2c4.com/wireguard/windows?go-get=1
go: golang.zx2c4.com/wireguard/windows@v0.0.0-20201130211600-76ef01985b1c:
invalid version: unknown revision 76ef01985b1c
[-] Failed with error #1.
[+] Rendering icons
[+] Assembling resources x86
[+] Building program x86
get "golang.zx2c4.com/wireguard/windows": found meta tag
get.metaImport{Prefix:"golang.zx2c4.com/wireguard/windows", VCS:"git",
RepoRoot:"https://git.zx2c4.com/wireguard-windows"} at
//golang.zx2c4.com/wireguard/windows?go-get=1
go: golang.zx2c4.com/wireguard/windows@v0.0.0-20201130211600-76ef01985b1c:
invalid version: unknown revision 76ef01985b1c
[-] Failed with error #1

Thanks,
Mani

Re: [Windows] Unable to build latest wireguard missing i686-w64-mingw32-windres

[Vladyslav Ivasyuk]

Hi,

the problem with "unknown revision" is happening because git history
was rewritten. There are two projects which are kept in branches of
the Windows WireGuard client project. Those are "github.com/lxn/walk"
and "github.com/lxn/win" and branches for them are "pkg/walk" and
"plg/walk-win" respectively. Both branches have a number of
customization commits which are kept at the top of the git history.
Hence sync with lxn's code is done with rebasing and then force
pushing. So after the sync, old commit id is lost and replaced with a
new one. Each time those branches are updated, you can also see the
"mod: bump" commit in the main branch. All commits before that will
not work anymore. Therefore old tags are not reliable too.

Probably, it can be fixed by keeping separate branch for at least
every tag, so build on tags does not break. Though, it would be better
to create a new branch on every update/sync. Another options to
consider are maintaining the lxn in a separate repository or keep
changes as a set of patches.

Best,
Vladyslav