On Wed, Aug 12, 2009 at 17:14:08 -0500, Brian Lewis wrote: > Please take a look and let me know what's wrong and/or add to the > Setup.hs so it works on your platform. It would be cool if all the > wxHaskell packages were just more normal packages on HDB.
First: wxcore doesn't compile against the default wxWidgets on MacOS X, which is fine because I've gotten used to building my own wxWidgets. Second: the old wxHaskell had a convention where if a wx-config lives in /usr/local/wxhaskell/bin that we would use it. This would make it a bit more straightforward to cabal install wxcore, i.e. without having to do something like PATH=/usr/local/wxhaskell/bin:$PATH cabal install wxcore. Can you think of a good/simple mechanism to let people use their own wxWidgets?? 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... Thanks! -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgp4Gpfj6beu8.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
