Re: Link problem

Subject: Re: Link problem

From: Chris Espinosa <email@hidden>

Date: Wed, 30 Jan 2008 09:11:53 -0800

Delivered-to: email@hidden

On Jan 30, 2008, at 3:40 AM, Daniel Luis dos Santos wrote:

i have a project that was created as a bundle. I then read the documentation on bundles and figured out that it wasn't the kind of product that I wanted. I wanted a dynamic library. I then changed the mach-o type to dynamic library in the target's build settings.

Then I created another target that depends on the first target. This one uses a class compiled from the first target. I added the first target as a dependency of the second. I get an error when linking the second target saying that it can't find the symbol for the class used from the first target.

I was expecting the target dependency would do this. I am wondering if it is because of the product type. In the build settings for the first target, the general pane still shows bundle as the product type. Can this be changed ?

If you have a dynamic library target and a target that's a client of that library, you need to perform three separate, independent, but required steps:

1) Add the library's target to your client target dependencies, to make sure it's up to date at link time

2) Add the library itself to your client target, to actually link to it

3) Add the library itself to a Copy Bundle Resources or Copy Files build phase, so your client finds the dylib at runtime

Yes, it would be nice if Xcode did all three at once.

Chris

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/xcode-users/email@hidden This email sent to email@hidden

Follow-Ups:

Re: Link problem
- From: Daniel Luis dos Santos <email@hidden>

References:

>Link problem (From: Daniel Luis dos Santos <email@hidden>)