RE: winapi update

[Patrik Stridvall]

> Btw, what does make filter do?
>
> Your post to wine-patches says it's nice an all but it does not say
> what it does.

Try and run it it is self describing. :-)

Since Alexandre didn't apply the Makefile patch, running it is
a little awkwark. Will fix that it later versions though.

Try do:
cd wine
./tools/winapi/make_filter make

You can also give it parameters like 
./tools/winapi/make_filter make clean

Warning "make clean" doesn't look that good currently.

PS. It filters the make messages and only display important messages.

It might not always work 100% though, but I will fix problems as I
find them. I wrote it many months ago and have run it from time to
time since, so most issues have been fixed.

The reason I wrote it was that I was irritated that important messages
scrolled of screen.
> If it's nice isn't it worth advertising to the Wine
> developper community?

I had intended to do that if but since I was unsure that Alexandre
would apply my Makefile patch I decided to wait until it could present
a better "user interface". But by all means test it.

winapi update

[Francois Gouget]

On Fri, 27 Jul 2001, Patrik Stridvall wrote:
[...]
> PS. It filters the make messages and only display important messages.

Ah, ok.

I tried it.
   The first run gave me a number of errors:
$ ./tools/winapi/make_filter make
Use of uninitialized value in string eq at tools/winapi/make_parser.pm line 82, <IN> line 1.
Use of uninitialized value in string eq at tools/winapi/make_parser.pm line 82, <IN> line 1.
Use of uninitialized value in pattern match (m//) at tools/winapi/make_parser.pm line 82, <IN> line 1.
Use of uninitialized value in string eq at tools/winapi/make_parser.pm line 82, <IN> line 1.
Use of uninitialized value in string eq at tools/winapi/make_parser.pm line 82, <IN> line 1.
Use of uninitialized value in string eq at tools/winapi/make_parser.pm line 82, <IN> line 1.
Use of uninitialized value in string eq at tools/winapi/make_parser.pm line 82, <IN> line 1.
Use of uninitialized value in string eq at tools/winapi/make_parser.pm line 82, <IN> line 1.
Use of uninitialized value in concatenation (.) or string at tools/winapi/make_parser.pm line 30, <IN> line 1.
make_filter: : can't parse output: 'Make.rules.in is newer than Make.rules, please rerun ./configure!'

Would it be possible to have the messages pass through as-is when
they are not recognized (with the current directory for context)?
   So I ran ./configure and tried again and it was much better. What
is a bit strange is that it did not leave a single message around. A
third run on a file that I know generates a warning gave me the
following:

$ ./tools/winapi/make_filter make
make_filter: gcc: can't parse output: 'd3ddevice/mesa.c:817: warning: unused variable `xvis''

It looks like there's an incompatibility with colorgcc.
   Colorgcc is a perl script that you can wrap around gcc and g++ and
which colorizes the resulting output. So warnings appear in yellow,
errors in red, some other items in cyan, ... It works pretty well as
long as your xterm background is black like in the latest Debian. To use
colorgcc you simply add symlinks to colorgcc in your path:

$ ll /usr/local/bin/gcc /usr/local/bin/g++
lrwxrwxrwx    1 root     staff          17 Apr 27 12:37 /usr/local/bin/g++ -> /usr/bin/colorgcc*
lrwxrwxrwx    1 root     staff          17 Apr 27 12:37 /usr/local/bin/gcc -> /usr/bin/colorgcc*

So it must be the controls characters added by colorgcc that confuse
make_filter.

--
Francois Gouget         [e-mail]        http://fgouget.free.fr/
 Advice is what we ask for when we already know the answer but wish we didn't
                                 -- Eric Jong