Re: linking to a static lib and *not* a dynamic lib when both are present
Re: linking to a static lib and *not* a dynamic lib when both are present
- Subject: Re: linking to a static lib and *not* a dynamic lib when both are present
- From: Ladd Van Tol <email@hidden>
- Date: Fri, 21 Mar 2008 08:30:04 -0700
On Mar 21, 2008, at 4:07 AM, Tyler Daniel wrote:
It seems my fears are substantiated. At version 3.0, I guess the
Xcode team doesn't consider the inability to specify the type of
library a bug. I hope that changes in the future, and in the
meantime I'd say that the UI is a bug, showing libsomething.a in the
Link Binary with Libraries stage when the decision is actually left
up to the filesystem.
Don't hold your breath on this one. I filed a bug (3716243) on the
same issue in 2004, and it was marked as a duplicate of an even older
bug (2725744).
I have a simple metric for determining if Apple will fix an Xcode bug:
1. Does this bug affect Apple engineers?
2. If yes, fix bug
3. If no, do not fix bug
All kidding aside, I think Apple might benefit from deeper insight
into how non-Apple engineers use Xcode. Not being able to pick dynamic/
static linkage from the GUI is easy for Apple to ignore, because Apple
can just ship the pertinent dylib with the OS. Similarly, the lack of
support for non-Unix line endings in FileMerge is easy for Apple to
ignore, because they don't port Windows apps very often.
- Ladd
_______________________________________________
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