Hello Arthur722
2008/6/25 Arthur Norman <[EMAIL PROTECTED]>:
> What I wondered about was proposing a compiler flag so that regardless of
> the way the compiler had been built and was hosted it could be told which
> style (cygwin vs native windows) file names it should cope with? Would
> that be seen as generally useful and might it get into gcc?
>
> For what it is worth, when building 32-bit apps on Windows I am typically
> in cygwin and using "gcc -mno-cygwin" as my way of using mingw.
>
> Any advice/thoughts welcome!
Well, to have in gcc the ability to use native pathes wouldn't be so
bad. I am just not sure if the cygwin environment would treat the dos
pathes proper. But if this option (maybe something like
--no-cygwin-mapping) works, I think it has a good chance to get into
gcc. But why not simply using the native toolchain within cygwin? I
used this often and it worked for me well.
The -m32/-m64 is on my todo list. I hope I will find some time to
enable this. I agree that this would be of great help for mingw users.
Regards,
Kai
--
| (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
