On Jan 25, 2007, at 07:15, Nicola Pero wrote:
So we could have a small makefile fragment, let's call it find-
gnustep.make,
that searches for gnustep-make on disk and sets GNUSTEP_MAKEFILES
to the best
match. I'll write that makefile fragment, and it will be
maintained inside
gnustep-make.
I don't get this one, you want to let the fragment search for gnustep-
make? Where will it search? Isn't it expensive to search all
locations everytime? I'm not convinced that this can happen
automagically.
My configure scripts has options to specify the gnustep-make
installation you want to use (though of course it tests a few
hardcoded locations as a fallback, but only once, at configure time).
I think the 'configure' script should be maintained inside gnustep-
make (the script which generates the config.make, usually not a real
autoconf configure).
You probably don't want to run configure everytime you call make ;-)
BTW: personally I'm not quite sure whether I understand that /etc/
GNUstep.conf thing :-) Is it necessary or optional?
It is necessary. The reason is that it allows gnustep-make and
gnustep-base to have a common understanding of where the various
directories are.
The GNUstep.conf file describes the GNUstep filesystem and both
gnustep-make and gnustep-base read it to know where to find things.
Well, I'm talking about FHS, why would they need to know?
In an FHS the gstep-base just needs a (fallback) prefix like other
libraries to know where to look for associated files. Eg
./configure --prefix=/opt/gnustep-base-15
it would then know where to look for resources etc (because thats
fixed in FHS).
Greets,
Helge
--
Helge Hess
http://www.helgehess.eu/
_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev