How do I port Go 1.18 to Windows XP?
>>107605938gemini.google.com
>>107605938You'll have implement the runtime using the Win32 API
>>107606385Surely I could just change the runtime to remove unsupported functions?
>>107606423Why the fuck are you asking me? Get it. Chop chop.
>>107605938>Go 1.18why that version specifically?
>>107606491op probably just wants to run some specific Go software on windows XP, however they are too retarded to realize that doing anything on windows XP is not worth your time because windows XP is hot dogshit
>>107606491I am writing my rpg editor in it.(I could use a more modern version but that would make porting even more difficult and also I think windows 7 is not supported anymore, so I would have to port to more targets)
>>107606507It is not for me. the areas of the world where rpg games are popular are also the areas where windows xp is popular. think Japan, Thailand, China.
>>107606530you're flat out of luck, porting go to any operating system is likely not a simple undertaking, AFAIK they use their own libc and everything there may be some way to use XP with modern programs via kernel extensions or something, i'd look into that
>>107605938What about Go 1.20?https://github.com/BieHDC/go-backportsNot my project
>>107606530>the areas where windows xp is popular. think Japan, Thailand, Chinalol XP isn't popular in any country now. even people in dirt poor African countries have moved on
>>107606567Thanks, that is all I needed. I am not sure about backwards compatibility, but it has 1.19 too so even if it doesn't work I will know what to change. How did you find it? I searched for a port like this for hours.
>>107606517> I think windows 7 is not supportedIt was intentionally broken for windows 7 after go 1.20 by an illegitimate check-in that used a new (or perhaps newly documented) function that appeared only after windows 7.Everything would have continued to work calling the old RTL function to get random data.So it was a cosmetic “magical thinking” change that only affects some crypto intentionally made to break windows 7 unnecessarily.I wish these hyper-religious windows zealots would find something else to do… like ditch digging.
>>107606606The author mentioned it in the (unofficial) Go matrix room two years ago
>>107606622why did they do it? was the new function that much better?
>>107606606>I searched for a port like this for hours.Keyword is backport. Another one for Win7 https://github.com/Snawoot/go-win7
>>107606684They imagined that microsoft told them to.It was a hallucination.A lot of them never learned common-sense shit like “if it ain’t broke, don’t fix it” or “do on to others… “ because they never had fathers that had to put up with shit and educated their children into adulthood.I just fucking forked go as soon as they did that.It’s not like they’ve done anything useful since then. I fixed the panic()s in their goddamn standard libraries long ago, so I’m no longer interested in their futile and meaningless gyrations,
>>107605938
>>107605938It works on win7 using vxkex, so you can probably just copypaste whatever function it's using out of vxkex and put it in your own DLL wrapper.>how do I make a DLL wrappergit gud
