Hello Peter, Sunday, November 12, 2006, 9:39:07 PM, you wrote:
> * Task point 3: drop dependencies on mingw32 functionality in the > libraries > Windows-native versions of Perl are available. > only library dependencies matter. we can run any external tools during > compiling process, be it compiled by msvc, mingw or even cygwin > For the most part, I agree with you--the part I don't quite agree > with are remaining dependencies on mingw/cygwin tools in order to > run GHC. As I understand it a Windows-native GHC would be able to > run without mingw/cygwin tools at all, so GHC binaries may be > distributed as Windows installs running under DOS or an IDE such as > Visual Haskell, that is, both GHC and programs compiled by GHC would > be Windows-native. A GHC dependency on Perl running under mingw > would run contrary to that concept: I mentioned Perl both for that > reason and to clarify whether my concept of the task scope was > correct. What do you think? seems that don't know the situation :) cygwin-compiled programs require cygwin.dll to run, this dll emulates Unix functions through Win32 API. mingw-compiled programs don't require any external files, they contain emulation of unix functions right inside executables itself. so there is absolutely no difference whether you run mingw-compiled or VC-compiled program btw, currently GHC produces mingw-compiled programs that is just native windows executables like produced by any other compiler. the reason why we want VC compatibility is to link with code produced by VC and nothing else. so we don't have any reasons to limit our use of mingw-compiled tools as long as they are shipped with ghc (like we now ship gcc, perl, ar and other tools) -- Best regards, Bulat mailto:[EMAIL PROTECTED] _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
