From: khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject: Re: libXpm.dll doesn't build with B20.1
11 Dec 1998 00:10:32 -0800
Message-ID: <199812101819.MAA07326.cygnus.gnu-win32@modi.xraylith.wisc.edu>
References: <6946-Wed09Dec1998192115+0100-vzell AT de DOT oracle DOT com>
To: "Dr. Volker Zell" <vzell AT de DOT oracle DOT com>
Cc: Cygnus <gnu-win32 AT cygnus DOT com>

"Dr. Volker Zell" <vzell AT de DOT oracle DOT com> writes:
> if [ -f /tmp/DLL_BASE_COUNTER ]; then true; \
> else echo 0x67000000 > /tmp/DLL_BASE_COUNTER; fi
> dllwrap -s --def Xpm.def --output-lib libXpm.a -o libXpm.dll data.o create.o 
> misc.o rgb.o scan.o parse.o hashtab.o 	 CrBufFrI.o CrDatFrP.o CrPFrBuf
> .o RdFToI.o WrFFrI.o 	 CrBufFrP.o CrIFrBuf.o CrPFrDat.o RdFToP.o WrFFrP.o 
> 	 CrDatFrI.o CrIFrDat.o RdFToDat.o WrFFrDat.o 	 Attrib.o CrIFrP.o CrPF
> rI.o Image.o Info.o RdFToBuf.o WrFFrBuf.o junk.o  -image-base `cat /tmp/DLL_B

Remember that you're creating shared library for win32, which needs to
resolve *all* symbols at link time, and as a consequence you must specify 
all the dependent libraries when building the DLL (eg., -lX11 etc).

fyi, if you don't explicitly specify an image base, dllwrap generates one 
based on the output filename (uses a simple hashing algorithm) and may be 
sufficient for 99% of the time. Unless of course you need to specify it 
for some other reason. ``dllwrap --dry-run ...'' shows what it's going to 
do without actually doing it.

Regards,
Mumit

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".