On 14/04/06, Peter O'Gorman <email@hidden> wrote:
> I'd be inclined to disagree. /usr/lib /lib and /usr/local/lib are all in
> the "system" search paths for the linker. When you specify an new system
> root, surely all the system search paths should be changed. For
> directories outside the standard framework and library search paths,
> they are only used if they exist in the new root. This seems perfectly
> legitimate to me.
On the other hand, when you specify an SDK you're just specifying an
SDK representing a certain version of the system libraries, headers
and frameworks. /usr/local/lib is obviously not supplied by the
system, so it doesn't really make sense to treat it as part of the
SDK...
The fact that SDKs are implemented by changing the root for the system
search paths in the compiler and linker is somewhat incidental to most
people's high-level goals.
It all depends on how you look at it, as Eric mentioned ;-)
-- Finlay
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
