RE: Problem building gnustep-base tools with MinGW

[Christopher Armstrong]

Hi

XSLT is #***ed on Windows. It compiles as a static library, and its 
imports end up overriding the imports in gnustep-base.dll when you do a 
"-lxslt", such that all of the libxml2 and gnustep-base exported symbols 
get obliterated (all the __objc_ and NS* functions). I don't know what 
the solution is, but I usually leave xslt out. If you have a copy of 
Visual Studio 6 lying around, the "depends" tool in it will give you an 
idea of what I mean (run it against gnustep-base.dll).

We should contact the xslt people and let them know about this, but 
likely they don't have the time to fix it as its a Windows compile 
issue. I'm not sure, but I think the gnuwin32 binaries with libxslt 
precompiled using VC++ may work. These are hidden on the sf download 
page of this project.

Regards
Chris

> > > lcomdlg32 -lmpr -lnetapi32 -lm -I.
> > >       
> > The only difference that I can see if that you have -lxslt ... could it be
> > anything to do with the problem ?
> >     
>
> xslt is installed since a very long time...
> But it seems you're right !!
>
> This morning i deleted everything and re-install from scratch and now it works
> with gnustep-make in c:/GNUstep, with gcc 3.4.2, without xslt.
> (I still cant use --enable-native-objc-exceptions but that's not so important)
>
> But if i install xslt, gnustep-base doesn't build !
> (i tried twice as i wanted to be sure :-)
>
> I build xslt from source without any oddity. It is installed by default in
> /usr/local - like any other library. And it is found by gnustep-base configure
> script :
>
> checking for xml2-config... /usr/local/bin/xml2-config
> checking for libxml - version >= 2.3.0... yes
> checking libxml/SAX2.h usability... yes
> checking libxml/SAX2.h presence... yes
> checking for libxml/SAX2.h... yes
> checking for xsltApplyStylesheet in -lxslt... yes
> checking libxslt/xslt.h usability... yes
> checking libxslt/xslt.h presence... yes
> checking for libxslt/xslt.h... yes
>
> I still dont understand all the problems i encountered :
> Why the old release version couldn't be built ? I'm (almost) sure they used to.
>
>