• 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: If build errors, then don't debug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: If build errors, then don't debug


  • Subject: Re: If build errors, then don't debug
  • From: Aaron Montgomery <email@hidden>
  • Date: Wed, 6 Sep 2006 12:51:26 -0700


On Sep 6, 2006, at 12:19 PM, Isaac Wankerl wrote:

Is there a way for me to issue a "build and debug" command to Xcode
and have it stop after the build if there were errors?  I have the
"continue building after errors" option turned on, but if there are
any build errors, I don't want to debug the app (actually it will
debug a previously built version).  Whenever this happens, it always
take me awhile to realize that the app I'm debugging doesn't make up
to the latest source code changes I just made.

I assume there isn't a way to do this so I logged radar enhancement 4719139.

I agree that Xcode should be smart enough to figure this out on its own, but one possible workaround is to add a shell script phase before the build that moves the old debug binary to a new location. I'm guessing that Xcode will stop when it cannot find the binary.


Aaron
_______________________________________________
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: 
 >If build errors, then don't debug (From: "Isaac Wankerl" <email@hidden>)

  • Prev by Date: Re: Class Model omits properties and operations of Java sources
  • Next by Date: Debugging JNI
  • Previous by thread: Re: If build errors, then don't debug
  • Next by thread: Debugging JNI
  • Index(es):
    • Date
    • Thread