|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
First, let me apologize for the lack of clarity in my previous posting, I had to rush away from my desk.
On Jan 9, 2006, at 4:11 PM, Scott Tooker wrote:
I've been clicking the "Build and Debug" button.
Someone else graciously tried to answer my question, and I wanted to clarify:
We have a project file with all of our source files inside (c++).
We have multiple targets, say 6 static library targets and one application target that depends on and links in the static libraries in the project file.
I believe that all of the static libraries use the same level of debug symbols, optimization, etc...
It seems that if I make changes in on of the static libraries, Xcode will compile it when I select Build and Debug with the application as the target. So, Xcode realizes that the file and the library which the target relies on has been changed...
Yet, my changes are effectively ignored.
Should I hit compile and then run the app? Perhaps I am misunderstanding the difference between Build and Debug as opposed to just Debug? I was guessing that Build and Debug would rebuild the app if necessary and debug in the new app while plain old debug would just debug the existing app I have.
Thanks for any information,
Lyndsey D. Ferguson
Software Engineer : Platforms Group
Nemetschek North America, Inc.
_______________________________________________ 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
|>Xcode ignores compiles changes, but debugs old code (From: Lyndsey Ferguson <email@hidden>)|
|>Re: Xcode ignores compiles changes, but debugs old code (From: Scott Tooker <email@hidden>)|
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.