[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PATCH: NSPathUtilities etc
From: |
Adam Fedor |
Subject: |
Re: PATCH: NSPathUtilities etc |
Date: |
Tue, 24 Feb 2004 10:35:40 -0700 |
On Tuesday, February 24, 2004, at 12:43 AM, Kazunobu Kuriyama wrote:
Sheldon Gill wrote:
<snip>
I think that such configuration definitions and conditional
compilation
switches would be best moved to a file, say "options.h", which can
then be
easily edited for various compile time preferences. I think it's a
better
way for gnustep-base to go, rather than relying on autoconf to
generate an
appropriate 'config.h' header which has to include such things in
line.
Does this mean that we couldn't use the configure options such as
--prefix and
--sysconfdir and we would have to edit the hypothetical "options.h"
manually?
I was thinking more along the lines of setting up the preferences in
gnustep-make (using --prefix and everything else as it is now). Then
the GNUstep.conf file is generated in gnustep-make (perhaps it needs to
be generated in gnustep-base as well so it can be installed by
gnustep-base (without having to install gnustep-make)).
When compiling gnustep-base, you have
DEFS= -DGNUSTEP_INSTALL_PREFIX=$(GNUSTEP_TARGET_INSTALL_PREFIX) \
[...] \
-DGNUSTEP_CONFIGURATION_FILE=$(GNUSTEP_CONFIGURATION_FILE)
I don't like having to edit 'h' files before compiling something.
That's what configure is for.