Re: Verbose explanation about the cygwin issue

2010-03-26 Thread GOUJON Alexandre
Sorry for the delay, First of all, I would like to explain why I tried to compile wine on cygwin. My first goal was to help wine as some of you improve wine on different systems (native 64 bits. WOW...). I knew that wine compiled well on MinGW but I'm not using it. Cygwin is, on my mind,

Re: Verbose explanation about the cygwin issue

2010-03-23 Thread Peter Rosin
Den 2010-03-22 17:47 skrev Steven Edwards: On Sat, Mar 20, 2010 at 2:49 PM, Alexandre Julliardjulli...@winehq.org wrote: And what about #ifdef __CYGWIN__ ? It sounds ugly but ... why not ? You can't use #ifdefs in winegcc. I suppose you could try to resolve __wargv dynamically at run-time.

Re: Verbose explanation about the cygwin issue

2010-03-23 Thread André Hentschel
Peter Rosin schrieb: Den 2010-03-22 17:47 skrev Steven Edwards: On Sat, Mar 20, 2010 at 2:49 PM, Alexandre Julliardjulli...@winehq.org wrote: And what about #ifdef __CYGWIN__ ? It sounds ugly but ... why not ? You can't use #ifdefs in winegcc. I suppose you could try to resolve __wargv

Re: Verbose explanation about the cygwin issue

2010-03-23 Thread Steven Edwards
On Tue, Mar 23, 2010 at 4:17 AM, Peter Rosin p...@lysator.liu.se wrote: So, you need to ask yourselves what you want to do. Do you want to build Cygwin dlls/executables (depends on Cygwin libc) or do you want to build MinGW dlls/executables (depends on msvcrt)? Mixing is not supported, and if

Re: Verbose explanation about the cygwin issue

2010-03-22 Thread Steven Edwards
On Sat, Mar 20, 2010 at 2:49 PM, Alexandre Julliard julli...@winehq.org wrote: And what about #ifdef __CYGWIN__ ? It sounds ugly but ... why not ? You can't use #ifdefs in winegcc. I suppose you could try to resolve __wargv dynamically at run-time. I was wondering if it was possible under

Re: Verbose explanation about the cygwin issue

2010-03-22 Thread Steven Edwards
On Mon, Mar 22, 2010 at 12:47 PM, Steven Edwards winehac...@gmail.com wrote: My thinking was, if we require mingw on cygwin, then that would solve the winegcc problem and the rest of wine could be built including wine msvcrt, applications that linked to msvcrt would of course have to use Wine

Verbose explanation about the cygwin issue

2010-03-20 Thread GOUJON Alexandre
Alexandre, (I hope I'm not being direspectful) your patch (561a3e643ea8b35adfc032d3afa979c622fcec23) did not work. I know that there is no Cygwin VM in WineTestBot yet to test such a patch. I think I was not very clear about the issue on cygwin so this time I'll be more .. verbose. Here is

Re: Verbose explanation about the cygwin issue

2010-03-20 Thread Alexandre Julliard
GOUJON Alexandre ale.gou...@gmail.com writes: To fix it, we need to add msvcrt include (not to link with msvcrt : it's a .o) ccache gcc-4 -D__WINE__ -c -o cmd.exe-iqnSoR-q4unrB.o cmd.exe-iqnSoR.c -I../../include -I../../include/msvcrt/ succeeds. At this point, we return from

Re: Verbose explanation about the cygwin issue

2010-03-20 Thread GOUJON Alexandre
Le 03/20/10 15:57, Alexandre Julliard a écrit : You can't add include or lib options, that will break the Mingw build. And what about #ifdef __CYGWIN__ ? It sounds ugly but ... why not ? Thanks

Re: Verbose explanation about the cygwin issue

2010-03-20 Thread Alexandre Julliard
GOUJON Alexandre ale.gou...@gmail.com writes: Le 03/20/10 15:57, Alexandre Julliard a écrit : You can't add include or lib options, that will break the Mingw build. And what about #ifdef __CYGWIN__ ? It sounds ugly but ... why not ? You can't use #ifdefs in winegcc. I suppose you