On Wed, 25 Feb 2004 01:35, Adam Fedor wrote: > On Tuesday, February 24, 2004, at 12:43 AM, Kazunobu Kuriyama wrote: > > Sheldon Gill wrote: > > <snip> > > 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 mean to continue support for --prefix and such. It doesn't we couldn't use the configure options. The hypothetical "options.h" would be edited manually but it's supposed to be set up that way. It's for compile time behaviours within the library and for defining some default values. > 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)). This is the line I was thinking of for generating the GNUstep.conf file. > 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. I don't like having to use configure everything I want to change some behaviour option or default location for something _within_ the library. For example, my patch makes PLATFORM_SUPPORT an optional thing. Should you have to re-run configure to turn it on/off? If not, where should the definition go? Regards, Sheldon _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
