Benoit Sigoure wrote:
No sorry, this was necessary. MSYS isn't enough, and using it wouldn't
have
enabled me to do what I do now. The shell still removes unecessary
backslashes
and MSYS can't automagically handles things such as:
gcc -I/home/build/... (which needs to be rewritten in
-IC:/cygw
Quoting Duft Markus <[EMAIL PROTECTED]>:
Hi!
Hi, please answer below the quote :(
http://en.wikipedia.org/wiki/Top-posting
Hmmm, what do you mean with "wgcc doesn't set the environment"? It's
true, wgcc doesn't, but why should it?? The thing is, that wgcc should
be the only one to run cl.exe
Quoting Howard Chu <[EMAIL PROTECTED]>:
Benoit Sigoure wrote:
Quoting Benoit Sigoure <[EMAIL PROTECTED]>:
[SNIP, see http://lists.gnu.org/archive/html/libtool/2006-11/msg00018.html]
Hello folks,
I think I finally succeeded: I can now build any UNIX program as long as its
code is portable on
Hello Benoit,
* Benoit Sigoure wrote on Tue, Nov 28, 2006 at 12:54:09PM CET:
>
> Now the question is: would consider support for VC++ in libtool? This would
> imply doing something similar to what wgcc does, that is: rewritting all the
> arguments (-I's, -D's etc) for VC++. I can (try to) contrib
Benoit Sigoure wrote:
Quoting Benoit Sigoure <[EMAIL PROTECTED]>:
[SNIP, see
http://lists.gnu.org/archive/html/libtool/2006-11/msg00018.html]
Hello folks,
I think I finally succeeded: I can now build any UNIX program as long
as its
code is portable on Windows with both mingw-gcc toolchain
Quoting Benoit Sigoure <[EMAIL PROTECTED]>:
[SNIP, see http://lists.gnu.org/archive/html/libtool/2006-11/msg00018.html]
Hello folks,
I think I finally succeeded: I can now build any UNIX program as long as its
code is portable on Windows with both mingw-gcc toolchain and MS VC++.
I thought th
