Am Sonntag, 12. Mai 2013 schrieb Ángel González:
> On 12/05/13 21:50, Tim Rühsen wrote:
> > A real solution would be a rewrite of the init stuff (I saw that already 
> > somewhere on the Wget 2.0 wish list or somewhere - don't remeber exactly).
> >
> > I already wrote this kind of code and would contribute it to Wget.
> > But i am unshure how to apply it to Wget. Since it would be a pretty big 
> > change, should i git-clone Wget and you merge later or do you create a new 
> > branch or ...
> >
> > Ah, than we again have to discuss that infamous c89/c99 thing.
> > AFAIR, the main argument against c99 came from Daniel Stenberg (Curl, 
haxx.se) 
> > who mentioned MS Visual C not being C99 ready (it will never be, said MS).
> > I just saw that Debian has MinGW cross compiler packets for Win32 and 
Win64 
> > with gcc 4.6, but I have no experience with those.
> > Does anybody know if that is a real alternative to MS VC ?
> >
> > Regards, Tim
> Yes, it is a real alternative as a compiler which works :)
> However, I'm not sure how much does wget compile natively in win32 in
> right now,
> either with VC++ or gcc, mostly due to autoconf and gnulib detection.


Thanks for the hint. I just installed Debians MinGW packages and it worked 
like a charm (except a minor compile issue in url.c).

For anyone who wants to try:
$ make distclean
$ ./configure --host=i686-w64-mingw32 --without-ssl --disable-ipv6
$ make
$ wine src/wget.exe http://www.example.com

I have no real Windows installation around to test wget.exe.
But assuming, it works: Is there any need to stick at c89 code ?
Or in other words: do we still have to support native Windows compilation with 
MSVC (couldn't these people install and use mingw) ?

Regards, Tim

Reply via email to