Hi, there are two features/options that I miss from QNX 4 when compiling.
Is there a way to get qcc/QCC to produce *.err files when there are
compiling errors?
Watcom stops trying to compile after, I think, 25 errors. To me, getting
a listing of 3255 errors is totally useless. Especially when using pterm
where you can’t scroll back to see the first error. Can the compilers be
told to stop after X nuimber of errors?
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
Hello Bill,
Hi, there are two features/options that I miss from QNX 4 when compiling.
- Is there a way to get qcc/QCC to produce *.err files when there are
compiling errors?
Not to my knowledge, I use redirection for these purposes.
ie:
qcc -Vgcc_ntox86 -c fred.c > err 2>&1
or
qcc -Vgcc_ntox86 -c fred.c 2>&1 | tee err
- Watcom stops trying to compile after, I think, 25 errors. To me, getting
a listing of 3255 errors is totally useless. Especially when using pterm
where you can’t scroll back to see the first error. Can the compilers be
told to stop after X nuimber of errors?
Not to my knowlege, you can redirect the output to the “err” file and
scroll it back and forward to examine errors 
Best Regards,
Marcin
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
Hi, there are two features/options that I miss from QNX 4 when compiling.
Is there a way to get qcc/QCC to produce *.err files when there are
compiling errors?Watcom stops trying to compile after, I think, 25 errors. To me, getting
a listing of 3255 errors is totally useless. Especially when using pterm
where you can’t scroll back to see the first error. Can the compilers be
told to stop after X nuimber of errors?
In pterm you can use ctrl+atl + up/down arrows or pgdown/up to scroll up.
You also set the scrollback buffer.
–
Wave++
“Wave++” <wavexx@apexmail.com> wrote in message
news:9pa9kv$7te$1@inn.qnx.com…
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
2. Watcom stops trying to compile after, I think, 25 errors. To me,
getting
a listing of 3255 errors is totally useless. Especially when using
pterm
where you can’t scroll back to see the first error. Can the compilers
be
told to stop after X nuimber of errors?In pterm you can use ctrl+atl + up/down arrows or pgdown/up to scroll up.
You also set the scrollback buffer.Yes, but not that many lines.
Yes I know I can increase the number of buffered lines but I don’t want it
that large.
In article <9pa131$t08$1@nntp.qnx.com>,
Tools Mail Account <tools@qnx.com> wrote:
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
2. Watcom stops trying to compile after, I think, 25 errors. To me, getting
a listing of 3255 errors is totally useless. Especially when using pterm
where you can’t scroll back to see the first error. Can the compilers be
told to stop after X nuimber of errors?Not to my knowlege, you can redirect the output to the “err” file and
scroll it back and forward to examine errors >
Greg Comeau export ETA: Dec 1 10% “End of Summer” Offer
Comeau C/C++ ONLINE ==> http://www.comeaucomputing.com/tryitout
World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90.
Comeau C/C++ with Dinkumware’s Libraries… Have you tried it?
“Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
“Wave++” <> wavexx@apexmail.com> > wrote in message
news:9pa9kv$7te$> 1@inn.qnx.com> …
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
2. Watcom stops trying to compile after, I think, 25 errors. To me,
getting
a listing of 3255 errors is totally useless. Especially when using
pterm
where you can’t scroll back to see the first error. Can the compilers
be
told to stop after X nuimber of errors?In pterm you can use ctrl+atl + up/down arrows or pgdown/up to scroll up.
You also set the scrollback buffer.Yes, but not that many lines.
Yes I know I can increase the number of buffered lines but I don’t want it
that large.
Well, if you’re issuing a single qcc command, a buffer of 100 lines will
suffice (unless you’re compiling c++ code).
Would be nice to use redirection in that way:
qcc /* args here */ 2| head >> err.log
Wave++
Hi, there are two features/options that I miss from QNX 4 when
compiling.
- Is there a way to get qcc/QCC to produce *.err files when there are
compiling errors?Not to my knowledge, I use redirection for these purposes.
ie:
qcc -Vgcc_ntox86 -c fred.c > err 2>&1or
qcc -Vgcc_ntox86 -c fred.c 2>&1 | tee err
The more complete & general version goes like
%.o : %.cc
qcc /compiler options go here/ -c $< > $.err 2>&1
if[ ! -s $.err] ; then rm -f $*.err ; fi
This rule will create a .err file for each source, and the second line gets
rid of empty .err files. All we need now is an IDE (I do miss vedit plus)
that will read the .err file and take the cursor to the offending line(s) of
source code:~(
Jim Douglas
“Jim Douglas” <jim@dramatec.co.uk> wrote in message
news:9pd9b1$6c2$1@inn.qnx.com…
The more complete & general version goes like
%.o : %.cc
qcc /compiler options go here/ -c $< > $.err 2>&1
if[ ! -s $.err] ; then rm -f $*.err ; fiThis rule will create a .err file for each source, and the second line
gets
rid of empty .err files. All we need now is an IDE (I do miss vedit
plus)
that will read the .err file and take the cursor to the offending line(s)
of
source code:~(Thanks Jim. That’s exactly what I was looking for.
“Jim Douglas” <jim@dramatec.co.uk> wrote in message
news:9pd9b1$6c2$1@inn.qnx.com…
[…]
rid of empty .err files. All we need now is an IDE (I do miss vedit
plus)
that will read the .err file and take the cursor to the offending line(s)
of
source code:~(
I don’t want to start a religious debate, but emacs will do this, across
multiple
files and directories.
Cheers,
Andrew
“Andrew Thomas” <andrew.nospam@cogent.ca> wrote in message
news:9psj6r$6f4$1@inn.qnx.com…
“Jim Douglas” <> jim@dramatec.co.uk> > wrote in message
news:9pd9b1$6c2$> 1@inn.qnx.com> …
[…]
rid of empty .err files. All we need now is an IDE (I do miss vedit
plus)
that will read the .err file and take the cursor to the offending
line(s)
of
source code:~(I don’t want to start a religious debate, but emacs will do this, across
multiple
files and directories.
I’m just starting to feel comfortable with vim, are you telling me I have
to learn yet another editor, lol!
Cheers,
Andrew
No, I think what Andrew is saying, is that if you learn Emacs you won’t
need an IDE, or perhaps even an operating system
-----Original Message-----
From: Mario Charest [mailto:mcharest@clipzinformatic.com]
Posted At: Tuesday, October 09, 2001 4:46 AM
Posted To: devtools
Conversation: Two options I miss
Subject: Re: Two options I miss
“Andrew Thomas” <andrew.nospam@cogent.ca> wrote in message
news:9psj6r$6f4$1@inn.qnx.com…
“Jim Douglas” <> jim@dramatec.co.uk> > wrote in message
news:9pd9b1$6c2$> 1@inn.qnx.com> …
[…]
rid of empty .err files. All we need now is an IDE (I do miss
vedit
plus)
that will read the .err file and take the cursor to the offending
line(s)
of
source code:~(I don’t want to start a religious debate, but emacs will do this,
across
multiple
files and directories.
I’m just starting to feel comfortable with vim, are you telling me I
have
to learn yet another editor, lol!
Cheers,
Andrew