gnustep-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] Header organization


From: Adam Fedor
Subject: Re: [RFC] Header organization
Date: Fri, 27 Jun 2003 08:56:26 -0600


On Friday, June 27, 2003, at 04:17 AM, David Ayers wrote:

Adam Fedor wrote:

I wanted to avoid links for MingW. But then if we have a Foundation directory, that screws up the apple-apple-apple combo. I don't really see a good way to solve both problems. Anyway, since we already have a hack work-around for MingW, I guess keeping the links would be OK.

Well, another proposal I was considering was similar to:

Headers/gnustep/fdn/Foundation/NS*.h
Headers/gnustep/base/GS.h

Headers/gnustep/apk/AppKit/NS*.h
Headers/gnustep/AppKit/GS.h

and on systems which had symlinks we would add a Foundation/AppKit symlinks in Headers pointing down, and systems without symlinks could be extended to use -I*Headers/gnustep/fdn / -I*Headers/gnustep/apk respectively. (I would use the symlinks where available to reduce the -I options we need.)


Well, the easy way to solve both issues, I guess, is to have in gnustep-base:

Headers/gnustep/Foundation (NS*.h)
Headers/gnustep/base (GS*.h)

For all *-gnu-* combos, we arrange to include "-I../Headers -I../Headers/gnustep" and for apple-apple-apple, we have just "-I../Headers". Of course, we install the headers in the normal place, i.e. Headers/Foundation and Headers/gnustep/base. There's somewhat of a disconnect between the compilation location of headers and installed location, but it's no worse than before.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]