Hello Simon, Tuesday, November 14, 2006, 12:09:43 PM, you wrote:
>>>> only library dependencies matter. we can run any external tools during >>>> compiling process, be it compiled by msvc, mingw or even cygwin > You two are talking about different things, I think. no, you misunderstood me. i'm talking about installed GHC. when GHC compiles programs for me, it's free to use any tools - even cygwin ones, after all. that is not important as long as these tools (and dlls they require) are installed as part of ghc installation. what we want (at least _i_ want) is to compile to VC-compatible obj files, so that they can be mixed with code compiled by MS compilers > 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. and the same applies to the *using* GHC. i don't see any problems with using tools of any sort as long as they are free and don't force any license for the compiled code -- Best regards, Bulat mailto:[EMAIL PROTECTED] _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
