Re: Xcode does not rebuild app when source file updated in dependent static library
Re: Xcode does not rebuild app when source file updated in dependent static library
- Subject: Re: Xcode does not rebuild app when source file updated in dependent static library
- From: Russell Finn <email@hidden>
- Date: Fri, 19 Oct 2012 12:45:42 -0400
At my office-mate's suggestion, I checked out Stack Overflow, and when
I couldn't find anything on first search, I tried writing up my
question to post there. Turns out when you do this, SO offers you a
pretty good list of related questions, and in one of them I found a
good potential workaround.
When you add the static library to your application target (as Jens
suggested, by using the Add button in the Link Binary With Libraries
build phase), the library is added to your project with its location
set Relative to Group (in the File Inspector). Changing this setting
to Relative to Build Products was sufficient to solve the problem in
my test case: an immediate Build and Run caused Xcode to correctly
relink my application (picking up the last change I'd made to the
library). I'm now off to apply this solution to my actual project's
workspace, which contains a half-dozen or more static libraries and
two separate applications.
In my opinion this is still a bug in Xcode, but it's much more
tractable with this workaround. (I'll update my radar shortly.)
-- Russell
P.S. Credit where credit's due: the original source of this workaround
is in the Apple Developer Forums at
<https://devforums.apple.com/message/419328#419328>. For those without
access to the forums, it is referenced in Stack Overflow at
<http://stackoverflow.com/a/11826682/34498>.
_______________________________________________
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