Jump to content


Voltago

Member Since 30 Oct 2004
Offline Last Active Apr 14 2009 12:38 AM

Topics I've Started

The WeiDU --out option

12 November 2004 - 02:12 PM

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.

Linux compile blues

05 November 2004 - 09:36 AM

Hi! I'm trying to build WeiDU on linux. My environment:
gcc-3.4.2
glibc-2.3.3
ocaml-3.0.7
I've uncommented and fixed the environment variables in 'Makefile' according to my environment setup. However, the xdiff build fails with this error messages:
Compiling C file xdiff/xemit.c
+ gcc -Wall -Wno-unused -D_FILE_OFFSET_BITS=64 -D_REENTRANT -O2 -march=pentium3 -msse2 -pipe -s -fomit-frame-pointer -falign-functions=64 -fno-stack-protector -c  '-Iobj/x86_LINUX' '-Izlib' '-Ixdiff' -I'/usr/lib/ocaml' 'xdiff/xemit.c'
In file included from xdiff/xinclude.h:45,
                 from xdiff/xemit.c:23:
xdiff/xmissing.h:38: error: conflicting types for 'memcmp'
xdiff/xmissing.h:38: error: conflicting types for 'memcmp'
xdiff/xmissing.h:42: error: conflicting types for 'memcpy'
xdiff/xmissing.h:42: error: conflicting types for 'memcpy'
xdiff/xmissing.h:46: error: parse error before "__extension__"
xdiff/xmissing.h:46: error: parse error before "__uint8_t"
xdiff/xmissing.h:46: warning: type defaults to `int' in declaration of `__s'
xdiff/xmissing.h:46: warning: data definition has no type or storage class
xdiff/xmissing.h:46: error: parse error before '}' token
xdiff/xmissing.h:46: warning: initialization makes pointer from integer without a cast
xdiff/xmissing.h:46: error: initializer element is not constant
xdiff/xmissing.h:46: error: parse error before "c"
After that, this is repeated ad nauseam:
xdiff/xmissing.h:46: warning: type defaults to `int' in declaration of `__u'
xdiff/xmissing.h:46: error: conflicting types for '__u'
xdiff/xmissing.h:46: error: previous definition of '__u' was here
xdiff/xmissing.h:46: warning: initialization makes integer from pointer without a cast
xdiff/xmissing.h:46: error: initializer element is not constant
xdiff/xmissing.h:46: warning: data definition has no type or storage class
xdiff/xmissing.h:46: error: parse error before "case"
Is this the fault of my build environment (esp. gcc version?)? Has anyone succeded to build WeiDU on a similar setup lately? Thanks!