Hi Brian, On Sat, Aug 15, 2009 at 21:58:20 +0100, Eric Y. Kow wrote: > > Third: I'm getting linker errors when I try to build something that > > uses wxHaskell... I think this may be due to the second point. It > > sounds like we'd need to pass some information to the package > > description that we write out...
I just tried doing this again and for some reason, this time it works! I can't figure out what I've done differently (perhaps setting my PATH to point to my version of wxWidgets not just for cabal configure and cabal build, but for cabal install?), but this is very encouraging. If I'm right, it means that thanks to you, we now have a fully Cabalised wxHaskell that installs in the user directory. That's pretty exciting for anybody using wxHaskell in their applications because it means we can tell people: 1. install wxWidgets 2. if it's a custom wxWidgets, set your PATH 3. cabal install my-application which is a big improvement! -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpW14kFGr7Dq.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
