|
From: | David Ayers |
Subject: | Re: [RFC] Header organization of -base & -gui |
Date: | Fri, 04 Jul 2003 16:10:17 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507 |
Adam Fedor wrote:
Perhaps we should make this separation between User and Developer even more clear by consolidating these options:--enable-multi-platform --(dis)able-flattened into something like:--enable-developer (Actually I like --enable-multi-platform as a more encompassing option).
I think this makes sense, but then again, I haven't been using --enable-multi-platform... I'll let you and Nicola decide on it, if no one else jumps in.
But back the issue at hand... Should we keep, or rather aim at supporting apple-apple-gnu? - and therefor stop relying on the gnustep/base gnustep/gui header indirection - with all the implications it has on NSCoding archives (but then again we have the same issue with apple-apple-apple)
With some feedback from others, I came up with this potential approach... configure option: --enable-multi-openstep - must be 'yes' on OS X and defaults to 'no' everywhere else when set to 'yes' (or symlinks are not available) produces: Headers/GNUstepBase/GS*.h Headers/GNUstepFoundation/Foundation/NS*.h Headers/GNUstepGUI/GS*.h Headers/GNUstepAppKit/AppKit/NS*.h uses extra -Ixxx/GNUstepFoundation -Ixxx/GNUstepAppKit when set to 'no' (and symlinks are available) produces: same as above plus.. Headers/Foundation -> Headers/GNUstepFoundation/Foundation Headers/AppKit -> Headers/GNUstepAppKit/AppKit won't use extra -Ixxx/GNUstepFoundation -Ixxx/GNUstepAppKitI don't think --enable-multi-openstep must necessarily imply --enable-multi-platform.
Cheers, David
[Prev in Thread] | Current Thread | [Next in Thread] |