[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnustep-make experiment
From: |
Matt Rice |
Subject: |
Re: gnustep-make experiment |
Date: |
Sun, 11 Feb 2007 07:02:06 -0800 |
User-agent: |
GNUMail (Version 1.2.0) |
On 2007-02-11 03:23:35 -0800 David Ayers <address@hidden> wrote:
Nicola Pero schrieb:
So how does is help with writing configure scripts?
Maybe something like?
GNUSTEP_MAKEFILES=${GNUSTEP_MAKEFILES:=`gnustep-config
GNUSTEP_MAKEFILES`}
if test -z "$GNUSTEP_PATHLIST"; then
. ${GNUSTEP_MAKEFILES}/GNUstep.sh
fi
Yes, I think gnustep-config still needs to go a bit further and add
GNUSTEP_CFLAGS
GNUSTEP_CPPFLAGS
GNUSTEP_LDFLAGS
and possibly some more stuff
as we still need to hard code the obsoleted
-I$GNUSTEP_SYSTEM_ROOT/Library/Headers, etc
I assume this will happen when --includedir/--libdir/--bindir etc, etc
are supported as per
the TODO in common.make:264
And then, once all the variables are set, how should we write
configure
script tests? (and which variables are we allowed to use?)
Should we
1) tweak the environment to allow AC_CHECK_LIB to work?
2) create our own:
- AC_CHECK_GNUSTEP_LIBRARY
- AC_CHECK_GNUSTEP_FRAMWORK
- AC_CHECK_GNUSTEP_NATIVELIBRARY
macros to be included in configure.ac scripts via GNUSTEP_MAKEFILES?
3) invoke 'make' with gnustep makefiles in some config subdirectory
during ./configure
4) other ideas which I may have missed?
It definately seems the autoconf way to check system capabilities
regardless of
platform, if one takes this stand AC_CHECK_NATIVELIBRARY seems out of
place
and you should call both
AC_CHECK_GNUSTEP_LIBRARY and
AC_CHECK_GNUSTEP_FRAMEWORK
I don't feel strongly either way
though about naming conflicts e.g. libInterfaceBuilder vs
InterfaceBuilder.framework
If we theoretically promote libInterfaceBuilder to a native-library
and take in to account the different ways people use GNUstep-make on
apple
a) using gnustep
b) just using gnustep-baseadd/make
theres currently no way to stop gcc from looking in
/System/Library/Frameworks etc
(well i believe there is in gcc svn) we can just add
/path/to/GNUstep/System/Library/Frameworks
to the beginning with -F option
and if its found it'll link against the GNUstep one... before looking
in system places
runtime is probably a whole other deal requiring environment variables
and stuff
but yeah 1) and 2) look good
or a combination of 1) + AC_CHECK_FRAMEWORK used to implement 2)
Re: gnustep-make experiment, Nicola Pero, 2007/02/10
Re: gnustep-make experiment, Christopher Armstrong, 2007/02/10
Re: gnustep-make experiment, Nicola Pero, 2007/02/11