Re: Xcode ignores compiles changes, but debugs old code
Re: Xcode ignores compiles changes, but debugs old code
- Subject: Re: Xcode ignores compiles changes, but debugs old code
- From: Steve Checkoway <email@hidden>
- Date: Tue, 10 Jan 2006 13:14:59 -0800
On Jan 10, 2006, at 1:56 AM, James Larcombe wrote:
3. The application has several static library targets that it
links together for the main application. The source is in the
library. The source is all in the project however....
I've been bitten by this one -- the linking step often doesn't get
run when you're linking against static targets. The build appears
to go through all the steps, but never links. You have to
manually delete the target (or add a custom build phase that
deletes it) in order to ensure that you end up with an up-to-date
executable. It's an absolute pain.
This probably seems often to be caused by having separate build
locations
for the static library and the main application. Xcode does not
support
this, and the symptoms (for me at least) are the linking problems
described
in this thread.
Are you sure that is true? For a long time, I had a static library
being built in once place and my application which was linking
against the library being built in another.
Make sure all the projects are building to the same location. There
are a
number of ways this can be done, but I did it by changing the Build
Location setting for each project to a folder called 'Build' at the
top of
the source tree (this means that it will work when the tree is
checked out
and built on a fresh machine with no faffing around).
I had the library being built in "$(SRCROOT)/build" and the
application being built in "$(SRCROOT)/.." Everything worked for me.
- Steve
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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