> What *is* our story for hslibs/Win32? > > We're trying to switch over to libraries/. > * Is libraries/Win32 a complete replacement for hslibs/Win32? > * Is it "alive"? (ie. does it work? does anyone use it)
I moved hslibs/Win32 over to libraries/Win32 and made the following changes: 1) Put it in hierarchial module namespace 2) Made it all compile (== pass through greencard) using latest Greencard version (i.e., using new FFI types instead of old ccall-era types.) I might also have compiled it with ghc or Hugs but I'm not certain. I certainly didn't link anything with it or test it although _I believe it won't take much more work to get it working_. To build it, you need to use with Microsoft supplied header files (because compiling Greencard code depends on these). Last time I looked, this meant that you had to use the Microsoft C compiler (distributed with the Visual C++ package and the documentation describes a line or two to add to your autoexec.bat so that you can use the compiler in batch mode). Following a disk failure, my laptop has an empty partition waiting for me to get round to re-installing Windows on it so, at the moment, I don't have Visual C so I can't take the development any further. -- Alastair _______________________________________________ Cvs-ghc mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/cvs-ghc
