On 9 Feb 2007, at 13:04, Matt Rice wrote:
On 2007-02-08 05:13:32 -0800 Nicola Pero <[EMAIL PROTECTED]
innovation.com> 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.
Here is an example -- put this at the top of your GNUmakefile,
just before include $(GNUSTEP_MAKEFILES)/common.make --
GNUSTEP_MAKEFILES = $(word 1, \
$(wildcard /usr/GNUstep/System/Library/Makefiles) \
$(wildcard /var/lib/GNUstep/System/Library/Makefiles) \
$(wildcard /usr/local/GNUstep/System/Library/Makefiles) \
$(wildcard /opt/GNUstep/System/Library/Makefiles) \
$(wildcard /System/Library/Makefiles))
This doesn't actually fix anything, if we're going to change the
GNUmakefiles so their usable without
having environment variables we might as well fix it for all cases
not just the most common ones.
I don't think there *is* a fix for all cases.
I'd certainly much rather have a solution which works for all common
cases (as Nicola suggests) than have a dependency on external stuff
like pkg-config which definitely won't work on some platforms unless
we install it as additional software when installing GNUstep.
Installing pkg-config with GNUstep is not a big issue in itsself, but
then you get problems if someone else installs a version configured
to look in a different place for its data files.
It seems to me that using pkg-config would be more fragile than what
Nicola suggests, but would be fine to include as a fallback to try
when all else fails.
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
