• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Xcode Build issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Xcode Build issues


  • Subject: Re: Xcode Build issues
  • From: "James Larcombe" <email@hidden>
  • Date: Wed, 7 Dec 2005 12:43:14 -0000

Paul Harvey wrote:

Using XCode 2.1 I've found on many occasions that when I make changes to a source file in my project then Build and Run, the changes I've made don't make it into the new dev build. I spent ages going around in circles until I realised that all my changes where not going in to the new build.

Do you have subprojects which build static libraries, which are then linked with your main application?

If so, you need to ensure that all the projects build to the same location,
otherwise Xcode won't know that it has to relink the executable. This is
an (undocumented?) limitation of Xcode that was discussed on this list
just the other week.

You can make them all build in the same location by (i) setting a custom
build location in your preferences or (ii) specifying the location relative
to each project in the 'Build Location' project setting. I prefer the latter
because it works when doing a fresh checkout from CVS.

_______________________________________________
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


References: 
 >Xcode Build issues (From: Paul Harvey <email@hidden>)

  • Prev by Date: Newbie - Using cppunit in XCode?
  • Next by Date: Re: XCode SCM and Passwords
  • Previous by thread: Xcode Build issues
  • Next by thread: Newbie - Using cppunit in XCode?
  • Index(es):
    • Date
    • Thread