On Thu, Nov 12, 2009 at 14:11:17 +0000, Jeremy O'Donoghue wrote: > $ WXWIN=/c/utils/wxWidgets-2.8.10 WXCFG=gcc_dll/mswu runhaskell Setup.hs sdist > Building source dist for wxcore-0.12.1.1... > Setup.hs: Error: Could not find module: Graphics.UI.WXCore.WxcClassInfo with > any suffix: ["gc","chs","hsc","x","y","ly","cpphs","hs","lhs"] > > I remember that we had some trouble with this last time. I thought the > 'extra-tmp-files' stanza indicated that we don't need these files in > the sdist. Eric, you fixed this for me last time. What did you do?
I think I replied too soon. The problem looks like an interaction between the fact that we expose our autogenerated modules and the fact that we generate them in a non-src directory (which is nice to do). One thing which makes the cabal sdist go is to change Setup.hs so that we no longer use autogen, but the source directory (slash "haskell"). I wonder if there is a better way though, for example, having a module that imports these autogen'ed modules and re-exports them. This would avoid dumping stuff into src -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpaY1ohpXLcO.pgp
Description: PGP signature
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
