Pocket Plane Group
Friends and Neighbors => Weimer Republic (WeiDU.org) => WeiDU => Topic started by: Wisp on February 14, 2016, 02:47:56 PM
-
WeiDU v239 still "d41d8cd98f00b204e9800998ecf8427e" has been released.
Download for Windows (http://www.weidu.org/%7Ethebigg/WeiDU-Windows-239.zip)
Download for GNU/Linux (http://www.weidu.org/%7Ethebigg/WeiDU-Linux-239.zip)
Download for OS X (http://www.weidu.org/%7Ethebigg/WeiDU-Mac-239.zip) (pending compiler)
Download the source code (http://www.weidu.org/%7Ethebigg/WeiDU-Src-239.zip)
Change log (http://weidu.org/~thebigg/README-WeiDU-Changes.txt)
Readme (http://weidu.org/~thebigg/README-WeiDU.html)
-
As for 238 before that, I built binary .deb packages of WeiDU 239 for Debian GNU/Linux users. They should work without any modification on any Debian derivative like Ubuntu or Linux Mint.
There you go to download them:
http://www.dotslashplay.it/ressources/infinity-engine/
-
The Mac version is unavailable. Could you please upload it as well?
-
Wisp doesn't actually have an OS X environment on which he can compile the Mac version, so he has to rely on one of the local OS X modders to build it for him.
-
I don't have a Mac either, but I was able to compile an OS X version on my virtual machine.
Download: WeiDU-Mac-239.zip (https://www.dropbox.com/s/n8qv9ewexsnn5de/WeiDU-Mac-239.zip?dl=1)
It hasn't been test extensively yet, since I don't own any Mac versions of the games. I would appreciate any feedback about whether it works flawlessly on a real Mac as well.
-
Thanks argent77! Now I can get the new Tweaks up to v239 across the board. :)
-
@argent77 what OS is on your VM? I vaguely recall discussions from a year or two ago that compiling Weidu on newer versions of OS X might not work for users with older OSes.
I'm using Mountain Lion (I'm stubbornly loyal to Lucida Grande.) I'd be happy to compile a Mac version of Weidu... if, erm, someone gives me instructions for how to "compile" stuff...
EDIT - Argent77's version seems to work for me!
-
I'm using an old OS X 10.7 ("Lion") installation.
The build instructions found in this document (http://www.weidu.org/~thebigg/new_compile.html) are relatively easy to follow. There are additional steps to perform though if you want to reduce file size even further.
-
OS X archive uploaded. Thanks, Argent77.
-
239 windows build have the same size as 238 > BWS won't download it and it will make certain mods fail: http://i.imgur.com/uCyynZh.png
wisp, please recompile it again (maybe use new commit) and put it to http://www.weidu.org/~thebigg/weidu.exe
-
File size is rather unsuitable to tell different versions of a file apart. I'd suggest to implement a hash function (e.g. MD5) into BWS instead.
-
checking filesize was fine for 15 years, It is the first time when such situation occurs. After recompiling with one more commit it will be fine again and for the next 15 years. Besides, how do you get md5 hash before downloading mod archive? Because when you download it, there is no point of calculating...
-
wisp, please recompile it again (maybe use new commit) and put it to http://www.weidu.org/~thebigg/weidu.exe
I'll pretend that was a joke. Good one.
-
I'll pretend that was a joke. Good one.
It's not a joke, he has always wanted the weidu.exe to be download-able without an archive structure around it. So the BWS can utilize it to update all the weidu.exe's without the need to copy it around places after extraction. Given that the archive name changes from each upload and so forth, it needs to be remade each time the archive is updated. Or made via horrors described only in the heritage of Cthulhu.
I am not sure, but if you could hide the file from browsers, so it's only download-able via a command structure or something(I don't really know how this all works, so... ) it would do... so long as you would tell that structure to ALIEN ... so he can utilize it in BWS.
-
I'll pretend that was a joke. Good one.
It's not a joke, he has always wanted the weidu.exe to be download-able without an archive structure around it. So the BWS can utilize it to update all the weidu.exe's without the need to copy it around places after extraction. Given that the archive name changes from each upload and so forth, it needs to be remade each time the archive is updated. Or made via horrors described only in the heritage of Cthulhu.
I am not sure, but if you could hide the file from browsers, so it's only download-able via a command structure or something(I don't really know how this all works, so... ) it would do... so long as you would tell that structure to ALIEN ... so he can utilize it in BWS.
Buh? The what now?
(There already exists a no-archive Windows WeiDU on weidu.org. If fact, there are two of them! But the other one gets the axe after next version.)
-
Uuh...
Well, technically there's no link to it in the page (http://www.weidu.org/~thebigg/)... I need to type it manually to download it. I know that's silly to note, but . but , but ... don't worry about it, now that you say it's there.
-
(There already exists a no-archive Windows WeiDU on weidu.org. If fact, there are two of them! But the other one gets the axe after next version.)
where? BWS use this one: Down=http://www.weidu.org/~thebigg/weidu.exe and even if it's 239, it has exactly the same filesize as 238. So now, BWS won't download new weidu it and all mods which depends on 239 will fail until you release 240 or recompile 239 adding one extra commit to alter the .exe filesize < this is what I've asked in my first post.
-
Down=http://www.weidu.org/~thebigg/weidu.exe and even if it's 239, it has exactly the same filesize as 238.
Well, yeah, that's what they said.
The file size doesn't need to change... if you rearrange the resources, remove unneeded bits and add needed ones. It's rare, but it happens. with ~240 updates at least ones.
You could make the BWS check the weidu.exe's own SHA-1 size and if it's BBE26DB... not download a new weidu.exe from the source...
Or MD5, then: 0419FC4....
Assuming a bit: Here's the actual info (http://oi65.tinypic.com/30t2rma.jpg). Gained via Explorer Suite's CFF Explorer.exe .
-
This problem can be resolved by simply by recompile weidu, not by writing lot of code for the one particular case which appears after 15 years. Besides, because of this bug: https://github.com/WeiDUorg/weidu/commit/f435761f3d076126d1ea9be95a16fc548f9b894d weidu needs a 'fix' release because otherwise changelog is useless for now.
-
Get real. A) There has already been almost 100 commits between 238 and 239. What exactly makes you think a recompile is going to produce a new file with different size? Even if it were to, I'm not going to break versioning or release a new version just to make up for a short-coming in your system. B) If the change-log bug was of the dignity that it required a quick fix, it would not have gone unreported for a year.