4 replies to this topic

[Voltago]

Well, the CLI help of WeiDU tells me:

--out X        emit all output files in directory X

So I installed Unfinished Business v13 (WeiDUv163) (on WinXP) using the command line

setup-ub.exe --out c:\output --yes

WeiDU successfully compiled, patched and installed all necessary files, but the c:\output folder was yawning empty afterwards, while I expected to find all files created and modified by WeiDU in there. Is --out broken or am I mistaken about its actual usage/purpose?

P. S.: In case you wonder why I would want to seperately handle the WeiDU-modified files: I am creating a new (gentoo) linux installer for BG2 (+mods) and want to circumvent certain difficulties with insufficient file write permissions. So far, basic game + tob + patches + static mods like TS install fine (it's just a question of dropping files in the right place after all), but WeiDU mods are giving me trouble.

Edited by Voltago, 12 November 2004 - 02:48 PM.

[Idobek]

This is not what the --out switch is used for at all. It is used in conjuntion with other command line options to specify an output directory. I don't think what you want to do is currently possible, it would require a new switch.

Wes should definately be told about any file permission problems, he can probably fix this issue.

[Voltago]

I did already file a feature request at pocketplane.net.
However the file permissions issue is not really a WeiDU bug, it's just part of my file setup. I use a clean, unwriteable bg2 install as basis, create an identical folder-structure elsewhere and create a symlink of every bg2 file inside this 'virtual install'. Naturally, installing a WeiDU mod against this setup is bound to fail, so I want to store the installation files somewhere else first.