[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Ant and ErrorParsers
|
Hi,
actually, it should be probably rather easy to
implement. As far as I understand, JDT part of Eclispe
has a very advanced support for ANT files and
hopefully also has a parser for error messages
produced by ANT. So, it should be just a matter of
copying several of JDT classes into CDT.
What do you think?
Regards,
Roman
--- Doug Schaefer <DSchaefer@xxxxxxx> wrote:
> I tend to agree. This would make a great enhancement
> request in Bugzilla so
> we don't lose it and hopefully someone picks it up
> and implements a
> solution.
>
>
>
> Cheers,
>
> Doug
>
>
>
> _____
>
> From: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Behringer, Martin
> Sent: Friday, November 25, 2005 9:59 AM
> To: CDT General developers list.
> Subject: AW: [cdt-dev] Ant and ErrorParsers
>
>
>
> Hi Mattias,
>
>
>
> thanks for the "-emacs" tip. That solved my problem.
>
> But nevertheless would it be great if Ant scripts
> were better supported by
> CDT without the batch indirection (eg by an ant
> builder that feeds the error
> parser) .
>
>
>
> Regards
>
> Martin
>
>
>
>
> _____
>
>
> Von: cdt-dev-bounces@xxxxxxxxxxx
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im
> Auftrag von Mattias Bertilsson
> Gesendet: Freitag, 25. November 2005 15:41
> An: CDT General developers list.
> Betreff: Re: [cdt-dev] Ant and ErrorParsers
>
> I agree with you about Ant vs. Make. And if you use
> the -emacs commandline
> option to Ant, it will not print the [<TASK>]
> prefixes and the CDT error
> parsers will work fine.
>
> /Mattias Bertilsson
>
>
> Behringer, Martin wrote:
>
> Hi all,
>
> we are using Ant scripts to build our C/C++ projects
> because they are much
> more powerful and portable than traditional
> makefiles.
>
> But unfortunately if we are invoking the scripts
> from within eclipse we are
> not able to get our compiler errors parsed by the
>
> error parsers.
> I see two ways of invoking the scrpts at the moment.
> Both work fine for
> compiling, but I can't get my errors parsed.
>
> 1. In the project properties dialog in the
> "builders" option I added a new
> Ant-Builder and registerd my build script. It
> executes fine, all the
> messages are displayed in the console, but the
> messages are not passed to
> the error parsers at all. How can I get the messages
> parsed by the CDT error
> parsers?
>
> 2. I the project properties dialog in the "C/C++
> Make Project" instead of
> invoking the standard build command, I execute a
> batch file to start ant. It
> executes fine and now all messages are actually
> passed to the error parsers.
> But unfortunately ant adds the prefix of the
> executed task before the actual
> error message. It looks like this:
>
> [compile] D:\project\boot.c:81: error: for each
> function it appears in.)
>
> Since the error parses dont't expect the task prefix
> "[compile]" they are
> not able to parse the messages properly and
> therefore are not able to put
> the into the problems view.
>
> What can I do to use Ant AND get my errors correctly
> parsed the the error
> parsers?
>
>
>
> Thanks in advance
> Martin
>
>
>
>
>
>
> _____
>
>
>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx <mailto:cdt-dev@xxxxxxxxxxx>
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> <https://dev.eclipse.org/mailman/listinfo/cdt-dev>
>
>
> > _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
__________________________________
Yahoo! Music Unlimited
Access over 1 million songs. Try it free.
http://music.yahoo.com/unlimited/
