Stupid Linker Question
Stupid Linker Question
- Subject: Stupid Linker Question
- From: James Bucanek <email@hidden>
- Date: Tue, 1 Feb 2005 09:08:03 -0700
Greetings,
I need a little wisdom from those that have been working with XCode for awhile.
I just added a Carbon call to my Cocoa/Obj-C project (LSCopyItemInfoForRef) and the build died when it got to the linker. So I played around, and finally decided to add the "ApplicationServices.framework" to my External Frameworks and Libraries. The program now links and runs just fine.
Poking around a bit, I discovered that the ApplicationServices.framework is actually a collection of other frameworks (about a dozen), most of which I'll never use.
Is there anything "bad" about linking against some large collection of frameworks that you don't reference? Am I bloating the link tables of my application, or creating run-time dependencies that I shouldn't?
On the other hand, it there anything "bad" about digging into a collection of frameworks like ApplicationServices and trying to link to just the one or two specific sub-frameworks directly? Should one stay out of the details of frameworks, just and one should stay out of details of packages?
--
James Bucanek <mailto:email@hidden>
_______________________________________________
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