[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-gcc-list] Gcc error message format (Oops)

From: Ron
Subject: RE: [avr-gcc-list] Gcc error message format (Oops)
Date: Wed, 8 Jun 2005 22:26:09 +1000

> "Colin Paul Gloster" <address@hidden> wrote:
> > sed "s/\([0-9]*\)\(: error: \)/(\1) \2/g"
> But don't forget that you gotta catch stderr, not stdout.
> -- 
> cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

Thanks Guys. That wasn't exactly right as it left the colon after the
filename. But a slight change fixed that. The compile line in the
makefile becomes:
Oops! Gotta get to bed earlier. This should be:

# Compile: create object files from C source files.
%.o : %.c
        @echo $(MSG_COMPILING) $<
        @echo '$(CC) -c $(ALL_CFLAGS) $< -o $@ 2> errors.txt' > Test.bat
        @echo 'sed "s/c:\([0-9]*\)/c(\1)/" errors.txt' >> Test.bat

I can now create, edit and compile a multi-file project in Visual Studio
with all the nice bits that go along with that, including now having the
editor navigate me to the error line (and their intellisense gizmo
really is good).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]