Re: FAQ: XCode not clearing errors and warnings messages
Re: FAQ: XCode not clearing errors and warnings messages
- Subject: Re: FAQ: XCode not clearing errors and warnings messages
- From: Chris Espinosa <email@hidden>
- Date: Fri, 5 Nov 2004 10:41:32 -0800
On Nov 5, 2004, at 2:02 AM, Stephane Denis (Core Design Ltd.) wrote:
When I have errors or warnings messages in the 'Messages Window' (The
one that list errors and warnings with yellow and red icons) they
never go away, even when I fix my program.
I've got some situations like having 'build success' with really no
more errors and warnings, but they are still displayed.
(even the yellows or red icons of the left margin are still here).
Worst, I need to close the project else, the errors and warnings
cumulate !
How to fix that problem ? Looks like XCode never clears its messages
flags
I've also notice that in some occassion, the error are not displayed
correctly in that message window, I need to open the output window and
look at the compiler result instead.
This has been covered on the list before; you can search the archives
with a query like this:
http://search.lists.apple.com/?q=errors+and+warnings&cmd=Search%
21&wf=0020&sp=1
There's a thread from last August with the answer:
On Aug 20, 2004, at 4:07 PM, Markian Hlynka wrote:
Ok, my project window's "errors and warnings" section is filled with
the last 3 days worth of compiles; every error or warning I've had is
in there. How do I clear this? It's driving my crazy!
Heiko Wichmann narrowed this down last week:
Since version 1.5 Xcode has problems with projects where the source
files are referenced by "Relative Path" and the path goes up (e.g.
../sources/main.cpp).
If you build "../sources/main.cpp" with compilation errors, the errors
are marked with a red circle.
If you correct the error, the compilation will succeed - but the Error
Marks do not disappear!
I filed a bug report with a description at bugreport.apple.com
(Problem ID: 3767854)
I've confirmed that this is indeed the case: if a source file is
Relative to Project but not "below" the project's directory in the
file system hierarchy, errors and warnings will not be cleared in the
Error and Warnings smartgroup or detail view. The Build Settings
window will, however, have the correct build results.
Here are two workarounds:
1) Move the project to the top level of the source, so that all source
files are peer to it or below its peers (i.e. no ".." in relative
paths)
2) Use the Source Trees feature of Xcode:
a) In Xcode Preferences, choose Source Trees
b) Click Add and add the name of the top level of the project (in
Setting Name) and the absolute path to it (in Path)
c) Open your project and select all affected source files, and choose
Get Info
d) In the Inspector, choose "Relative to <your Source Tree Setting
Name>" for the Path Style
All developers sharing this Xcode project file need to set the Source
Trees setting appropriate to their system.
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