Peter Tanski wrote:
Hello Bulat,
On Nov 13, 2006, at 4:44 PM, Bulat Ziganshin wrote:
Sunday, November 12, 2006, 9:39:07 PM, you wrote:
* Task point 3: drop dependencies on mingw32 functionality in the
libraries
only library dependencies matter. we can run any external tools during
compiling process, be it compiled by msvc, mingw or even cygwin
... As I understand it a Windows-native GHC would be able to
run without mingw/cygwin tools at all ...
seems that [you] don't know the situation :) ...
I guess I am trying to sort out the goals for the task and I tend
toward the relatively aesthetic option of creating a stand-alone GHC
compiler running on Windows (i.e., no extra tools shipped). In
addition to being aesthetic, mingw is GPL-licensed.
You are quite right about GHC compiled binaries--this whole idea came
up again as part of interoperability with .NET. I'm wrong about
removing the cruft--not part of the task at all.
You two are talking about different things, I think.
Yes we want a GHC install that doesn't include any of the mingw tools, this is
the whole point. However, during the GHC *build*, we are free to use
cygwin/MSYS/mingw tools as much as we like - this is what Bulat is referring to.
Dropping the use of cygwin/MSYS for the build system is a lot of work for not
much gain right now.
Cheers,
Simon
_______________________________________________
Cvs-ghc mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-ghc
