Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
Re: XCode4 force relink when static library change
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode4 force relink when static library change



On Oct 31, 2011, at 5:50 AM, Bruno Berisso wrote:

> I can complete the first requirement, but the second one is driven mi creasy. When I change some code in "B" and execute "A" Xcode compile the project "B" but don't relink to "A" with the last version of "B". Instead keep using the previous version of the library. So every time I change "B" I must clean the entry project to force Xcode to relink to the last version of "B".

This should work, so something’s clearly wrong with the way the project/workspace is set up, but without details it’s hard to give advice.
- What version of Xcode?
- Are the two projects in a common workspace (Xcode4), or have you added the B project to the A project to set up a dependency?
- Are you sure that the B library that A links is the exact same build product created by the B project?

—Jens

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >XCode4 force relink when static library change (From: Bruno Berisso <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2011 Apple Inc. All rights reserved.