Richard Frith-Macdonald schrieb: > > On 24 Jan 2007, at 14:10, Matt Rice wrote: > >> On 2007-01-24 04:17:17 -0800 Nicola Pero <[EMAIL PROTECTED] >> innovation.com> wrote: >> >>>> attached is just sort of an experiment in getting rid of GNUstep.sh >>>> to compile stuff >>> >>> If you use trunk, you don't need GNUstep.sh to compile stuff ... ;-) >>> 1. add /usr/GNUstep/System/Library/Libraries and /usr/GNUstep/ >>> Local/Library/Libraries to /etc/ld.so.conf and run ldconfig >>> 2. add /usr/GNUstep/System/Tools and /usr/GNUstep/Local/Tools to >>> your PATH >>> 3. set GNUSTEP_MAKEFILES=/usr/GNUstep/System/Library/Makefiles >>> and you're ready to go. Once we use FHS, then libraries and tools >>> will automatically be in your PATHs, so you would need to: >>> * do nothing to use GNUstep >>> * set the single variable GNUSTEP_MAKEFILES to compile GNUstep stuff >>> and you can also easily switch between different installations by >>> using configuration files. >>> Thanks >>> PS: investigations are still welcome though ;-) >> >> >> In that case I still think that pkg-config support would be >> worthwhile, as GNUstep is then totally isolated >> theres no way for an external shell script/autoconf to know anything >> about GNUstep really >> since GNUstep.conf put anywhere and they can no longer rely on >> environment variables, >> >> I've come across at least 2 instances of needing the environment >> variables >> GDL2 needs to attempt to link to the Gorm libraries to see if it >> should enable building of the GDL2 Gorm palette >> and in porting aquaterm, and the gnuplot adaptor for aquaterm, it >> needs to also look for a lib in the GNUstep heirarchy >> to enable that. > > > I find this discussion confusing ... > > I had assumed that the point of not using GNUstep.sh was for things > which did not want to know anything about GNUstep. That seems > reasonable enough... after all, why should you want to know about where > resources are if all you want to do is run a program? > > However, when you talk about GDL2 wanting to know where the Gorm > libraries are, you obviously DO want to know about GNUstep resource > locations, and you can easily get the information by running GNUstep.sh > ... so why do you want to not run it? What is the benefit of *not* > running GNUstep.sh for scripts which want to know about GNUstep?
It's not stricty GDL2 in this case but ./configure of GDL2 which want to tweak make file fragments dependent on what's available. So maybe we need some tool in the path to query the values. Something like gnustep-config akin to apxs and xml2-config. Cheers, David _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev