Re: "Build succeded (2 errors)"
Re: "Build succeded (2 errors)"
- Subject: Re: "Build succeded (2 errors)"
- From: Chris Espinosa <email@hidden>
- Date: Mon, 16 Jan 2006 12:22:28 -0800
On Jan 16, 2006, at 8:09 AM, James Larcombe wrote:
Does anyone else find that Xcode 2.2 will often report a
build success when there were actually errors in some of
the source files?
This is particularly annoying if you used the 'Build and
Debug' command. Then the application will happily launch
in the debugger even though it's not built correctly, so
if you've made some changes with a few un-noticed syntax
errors then you can spend minutes wondering why it's the
changes aren't having any effect, until you realise that
it never built in the first place.
Is this expected behaviour?
Yes and no.
This happens because Xcode simply orchestrates the activities of a
variety of command-line tools like gcc, ld, Rez, cp, etc. All those
tools a) produce text output to stdout and stderr and b) terminate with
a result code.
Xcode parses their output and determines how many errors and warnings
each tool produces, and senses the result code on exit of each tool.
It lists the errors and warnings in the Build Results window and counts
them, and if all tools have exited with status 0 (no error), it reports
Build Succeeded.
So if a tool reports in text something that Xcode parses as an error,
but returns status 0, then Xcode says "Build succeeded (1 error)" or
the like. This could either be a bug in the individual tool, or in
Xcode's parsing. You'll have to read the build transcript to find out
whether the parsed error is bogus, or the 0 result code is.
Do file a bug at http://bugreport.apple.com with the build transcript
so we can fix whatever bug is causing this.
Chris
_______________________________________________
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