I don't know if the reading of the documentation would eventually give this info, but it seems to me very deep to dig!

I found a nice file in the lib directory called "WIN32API.CSV" which allows one to find that 'undefined reference' even from the command line¹!

HTH

-- 
Cesar Rabak
GNU/Linux User 52247.
Get counted: http://counter.li.org/

[1] it just requires you know how to demangle the reference and the line coming will give you a clue of the header and the (export) library it is supposed to be.

Thanks for the tip!
I presume by "command line" you mean using "GREP"?

In article <3E64082D.7090100@uol.com.br>, Cesar Rabak says...
>
>I don't know if the reading of the documentation would eventually give this info, but it seems to me very deep to dig!
>
>I found a nice file in the lib directory called "WIN32API.CSV" which allows one to find that 'undefined reference' even from the command line¹!
>
>HTH
>
>-- 
>Cesar Rabak
>GNU/Linux User 52247.
>Get counted: http://counter.li.org/
>
>[1] it just requires you know how to demangle the reference and the line coming will give you a clue of the header and the (export) library it is supposed to be.
>

Keith Fuller escreveu:
> Thanks for the tip!
> I presume by "command line" you mean using "GREP"?
> 


Yes! I was thinking in grep. More adventurous ones may start to build an AWK
or Perl script, but this would turn the subject OT for this NG ;-)



-- 
Cesar Rabak
GNU/Linux User 52247.
Get counted: http://counter.li.org/