Re: [xslt] Windows build

[Morus Walter <morus walter tanto-xipolis de>]

Le grande pinguin writes:
> On Mon, Sep 30, 2002 at 03:20:44PM +0200, Igor Zlatkovic wrote:
> > > Igor, what i don't understand: does this 'double build' apply only to the
> > > Win/nn part f the build process or did you change the *nix build as well?
> > > In the later case i would strongly object.
> > 
> > Hehe, Daniel would roast my liver for breakfast had I done that to Unix :-)
> > 
> > All I have done affects only Windows build, only with MSVC compiler and that
> > only if executed through the makefile in ./win32. No other platform-compiler
> > combination will ever notice anything.
> 
> Ah, you just saved your live, i was allready sharpening my knifes ;-)
> 
>  Ok, thank's for the info
> 
Doesn't libtool do double build automatically?

At least under linux/gcc I get something like

/bin/sh ./libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include       -g -O2 -Wall -c encoding.c
rm -f .libs/encoding.lo
gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include -g -O2 -Wall -c encoding.c  -fPIC -DPIC -o .libs/encoding.lo
gcc -DHAVE_CONFIG_H -I. -I. -I. -I./include -I./include -g -O2 -Wall -c encoding.c -o encoding.o >/dev/null 2>&1
mv -f .libs/encoding.lo encoding.lo

for each source file...
The *.lo go to the shared library, the *.o to the static ones.

Or did I misunderstand something?

greetings
	Morus