Re: [RFC/make] Extend Framework support II

[Nicola Pero]

> > Given this discussion, the suggestion seems now to be to change
> > GNUSTEP_INSTALLATION_DIR to be / by default for frameworks, applications
> > and bundles, but to remain GNUSTEP_LOCAL_ROOT for libraries.
> > 
> > Of course, GNUmakefiles which hardcode a GNUSTEP_INSTALLATION_DIR wont'
> > work cleanly.  That's entirely correct because GNUmakefiles should never
> > hardcode a GNUSTEP_INSTALLATION_DIR :-), unless they are system libraries
> > like gnustep-base or gnustep-gui (which pose no problem since you can't
> > have them on apple-apple-apple, that's why they are system libraries after
> > all, they compose the basic gnu-gnu-gnu library combo).  Software should
> > install by default in whatever the default installation directory is on
> > that platform, unless the user decides otherwise on the command line.
> 
> I have no issue with GNUSTEP_INSTALLATION_DIR defaulting to '/' on 
> apple-apple-apple.  I have no issues with removing the predefined 
> GNUSTEP_INSTALLATION_DIR's in the GDL2, GSWeb and related projects (yet 
> I'd have to coordinate it with Manuel and David W.)  But again, please 
> consider granting the right to have a (or even multiple) "GNUstep 
> Installations" on OS X even for apple-apple-apple.
> 
> It's not one or the other here.  It just makes the "GNUstep 
> Installation" case work consistently with the rest of the GNUstep 
> infrastructure.  I know that Foundation and AppKit are not located 
> there.  And yes I understand why you view installing it with 
> GNUSTEP_INSTALLATION_DIR=/ as the more consistent approach.  I just 
> happen to disagree.  It's a great feature that GNUstep can integrate 
> with different OPENSTEP implementations this way.  I just don't see the 
> justification of not allowing the alternative configuration, which can 
> integrate just as well and has the option of allowing multiple "GNUstep 
> Installations".  (I'd post an updated simplified patch, but I currently 
> can't reach the machine I'd like to test it on first.)

Ok - so you want to install all your stuff, including frameworks, into
GNUstep directories outside of the Apple ones.

I don't think it's a good way of doing things, but I also agree it's a
reasonable request for a power user to be able to use gnustep-make in such
a way if you so wish, and the current code doesn't allow you to do it.

So, send me the patches to add -F and YDLIB_XXX on Apple and I'll commit
them. :-)

I'd still like to preserve the defaults for it to be to use it only as a
build system, so maybe the -F and DYLIB_XXX code should be turned on only
by a configure flag.  I'm not sure yet, but you'll have the possibility of
installing frameworks in gnustep-make's installation directory if you feel
that's what you need, and I'm sure a ./configure flag won't scare you that
much.

Thanks.  Useful discussion it seems :-)