So, part of the problem is that I am using my own build system (Blueprint) rather than Cabal, which I would like to test someday to make sure it works under windows; problems like screwing up the file paths are exactly the kind of thing that I worry about happening. :-)
And part of the reason that I developed and am using my own build system is because I am mixing Fortran and Haskell code, which is something that Cabal does not support in any meaningful use of the word "support" --- i.e., I don't count writing a parallel configuration and build system for the Fortran code and grafting it onto Cabal using a complicated assortment of hooks as being a meaningful sense of this word. :-) Cheers, Greg On Jan 18, 2010, at 1:52 PM, Stephen Tetley wrote: > Hello Gregory > > If the packages are FFI-free they "should just work" (ahem, perhaps > with some caveats about e.g. file paths - if they have data files > included). > > If they have FFI dependencies then a Windows emulator is going to have > to emulate Unix in turn (either via MinGW or Cygwin). It might be more > productive to simply label them as "Untested under Windows" and make a > reference to the FFI dependencies. > > Best wishes > > Stephen > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe _______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
