Re: Building a dynamic library using Xcode
Re: Building a dynamic library using Xcode
- Subject: Re: Building a dynamic library using Xcode
- From: Jens Alfke <email@hidden>
- Date: Sun, 30 Sep 2012 21:59:36 -0700
On Sep 30, 2012, at 8:20 PM, Chris Hanson < email@hidden> wrote: Xcode passes the names rather than the full paths of libraries (and frameworks) because that's the way the linker is commonly used on Unix platforms. In general when using ld on the command line — usually as a side-effect of invoking the compiler — you'd pass -lfoo or -framework Foo, rather than a full path.
I know how ‘ld’ works, but we’re using Xcode, not ‘ld’. In Xcode if I tell a target to link with a specific library file, then I want the target to link with *that file*. How Xcode accomplishes that by passing parameters to ‘ld’ (or if it even uses ‘ld’ at all under the hood) is purely an implementation detail that I shouldn’t have to care about.
This has caused me annoyance and frustration so many times over the years. It’s not a big deal but it’s one of those pain points that makes using one’s own libraries and frameworks harder than it should be*.
—Jens
* The worst of those being the inexplicable lack of support for building iOS frameworks. I have wasted literally weeks of time compensating for that. Literally. |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden