| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
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: http://lists.apple.com/mailman/options/darwin-dev/email@hidden
| References: | |
| >Problems building universal binaries using -isysroot (From: Tron Thomas <email@hidden>) | |
| >Re: Problems building universal binaries using -isysroot (From: Eric Albert <email@hidden>) | |
| >Re: Problems building universal binaries using -isysroot (From: André-John Mas <email@hidden>) | |
| >Re: Problems building universal binaries using -isysroot (From: "Peter O'Gorman" <email@hidden>) | |
| >Re: Problems building universal binaries using -isysroot (From: "Finlay Dobbie" <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.