Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: cmorgan
« on: December 29, 2018, 11:08:19 PM »

Roger that 😎. 32 it is. And for personal use x64 on a Win x64 system is overkill, as the x32 does just fine.
Posted by: Wisp
« on: December 29, 2018, 05:18:39 PM »

Unless you know your mod needs the 64-bit binary, distribute the 32-bit one. It has the widest compatibility.
Posted by: aqrit
« on: December 28, 2018, 04:05:48 PM »

The amd64 version is (mostly) for a select few mods with memory exhaustion problems.
If your mod doesn't have this problem then there is no need to use the amd64 version.
Posted by: The Imp
« on: December 28, 2018, 10:58:34 AM »

Has anyone tackled this yet?
No-pe.
I would make each an archive with the specific weidu tacked along. It's more work ... well, one could automate this with a windows script that takes a modname as a variable and a mod folder, and thus makes the different archives automatically. But even as I am not a programmer that can do that, I know it's possible. PS, there's already one .. for G3 mods.
Posted by: cmorgan
« on: December 27, 2018, 12:42:31 PM »

Reading through to catch up, but woefully behind.

We now have x32 and amd64 versions of WeiDU.
We still have autoupdate and packaging that uses setup-mymod.exe

What is considered best distribution practice for this situation?

I can see running a batch filke that querys the OS and renames one of two weidu.exe. Or have manual instructions to rename the correct file to setupo-mymod.exe. Or i could see not distributing weidu at all (shuppoing a folder with a .tp2 inside and requiring a user to rename or download and rename their needed version.

Or the cumbersome one - distribute

MyModv3_osx
MyModv3_lin
MyModv3_win32
MyModv3_win64

Has anyone tackled this yet?