| First off, I should have asked this earlier, what what version of Xcode are you running?
I'm assuming that you are using Xcode 2.2 when I respond below. On Jan 9, 2006, at 1:55 PM, Lyndsey Ferguson wrote:
Hi Scott,
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: What do I have to do to make Xcode compile and link in my changes when I make them?
To clarify, are you selecting "Build" or Build & Run" when after you make the changes, or are you always just selecting "Compile" to compile the single file and then running the app?
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.
You've set up all the target dependencies, correct? Simply linking a library into a target doesn't automatically create a dependency between the two targets.
Also, when you added the static libraries to the application target, you added the product references from the "Products" folder, correct? If you are using multiple build configurations, you want to make sure and use the product reference that Xcode generates since we keep those "in sync" with the active build configuration.
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.
As my question above implies, I think that somehow you are linking against the wrong copy of the static libraries, so you never get the ones you just built. That's my guess for now.
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.
No, you are making the right assumption about the differences bewteen "Debug" and "Build & Debug".
Scott
Thanks for any information, Lyndsey
-- Lyndsey D. Ferguson Software Engineer : Platforms Group Nemetschek North America, Inc.
|