On 2007-02-10 12:53:55 -0800 Matt Rice <[EMAIL PROTECTED]> wrote:
The objection i have with GNUstep.conf is it isolates gnustep from
the
rest of the world.
It sure is easy to use from shell scripts.... but how are you
supposed
to find it when
it could be anywhere, somewhere only gnustep can find.
Same applies to gnustep.pc ... it could be anywhere. Usually it's
in a
standard/common location, but you can say the same about
GNUstep.conf.
In this respect there is no difference between the two and its
therefore
illogical to use it as an argument either way.
No, If pkg-config cannot find the gnustep.pc the user has an
incorrectly set
up
pkg-config configuration, it the 'x' software package autoconf script
cannot
find
GNUstep.conf it has a correctly set up GNUstep, but external software
cannot
find it...
I could add --with-gnustep-conf= to tell gdl2 where to find
GNUstep.conf or
require GNUSTEP_CONFIG_FILE
so its configure script can look for libInterfaceBuilder if the user
has a
non-standard location for GNUstep.conf
but that just seems absurd.
Forgot to mention it'd also have to look for GNUSTEP_USER_CONFIG file
and do all that stuff GNUstep.sh does... it seems much more
complicated and
with possible configurations/documentation forking all over the place
in different
directions.. than just saying "pkg-config" is not configured
correctly.
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
