Hi Eric, 2009/11/12 Eric Y. Kow <eric....@gmail.com>: > > 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).
Yup - discovered that when I tried it :-( It's neat, but to be honest the old flex/bison user in me doesn't find it very offensive to generate code in src, provided that the clean target is implemented nicely. It has the advantage, for anyone working on the source code, of keeping everything nicely together. > 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 Does it solve the problem? I couldn't find any documentation on the extra-tmp-files: stanza, so I'm not really sure what it does. I suspect that the root cause of the problem is that we are trying to export modules which do not exist in a clean directory structure. Is it worth asking the cabal guys what they would suggest in this case? Jeremy ------------------------------------------------------------------------------ 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
