[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Long compiler error messages not readable in the Pr oblems view.
|
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Kim Lux
> Sent: Thursday, November 10, 2005 3:30 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Long compiler error messages not readable in the Pr
> oblems view.
>
> On Thu, 2005-11-10 at 14:18 -0500, Doug Schaefer wrote:
> > The best thing to do is to go back to the build console and look at it
> > there.
>
> The problem with that is on big builds the bug results are hard to find
> in the console text and further more the build text is larger than the
> console memory. So they aren't even there to look at in some cases.
>
> > The Eclipse Problems view really wasn't built to deal with long
> > messages, especially multi-line messages that we've had problems with
> > in the past (and current, I guess as well).
>
> I dunno what to say. This problem almost makes eclipse un usable for
> us.
Well, there are workarounds as you point out next.
> In Project -> Properties->"C/C++ Make Project"-> "Make Builder", I have
> "Stop on first build error" checked off. Why isn't it stopping ?
Make sure your build command doesn't have the -k option to make. Then it
should stop at the first failed compile.
> gcc always has long error printouts. How are other people using gcc ?
> Is there a flag for "short error descriptions" that I should be using ?
