Brian, Does this work better?
cabal install wx --configure-opt="--user --enable-split-objs --hcprof" (The key difference is the --configure-opt) On Sat, Aug 08, 2009 at 14:00:49 -0500, Brian Lewis wrote: > If there is some technical reason wx cannot be installed as a user > package, I'd like to know what it is. If there is a reason, the wx cabal > package should be changed to abort early if such an install is > attempted. It should not be trying to circumvent cabal's normal > procedure for package registration. I agree with you. This one stupid little issue makes wxHaskell difficult to install. It drives me absolutely nuts (1) because it's a stupid little issue (2) everybody trips on it and (3) we are ever so tantalisingly close to making wxHaskell easy to install if we could just fix this problem and (4) nobody seems to have the spare cycles to sit down and solve the problem. Things to know: - The wx package itself is fine. The problem is the wxcore package on which it depends. - Part of the issue is that the wxcore package requires a C interface to wxWidgets (which we call wxc, still shipped as part of wxcore). See this diagram of the pieces involved in wxHaskell http://bp2.blogger.com/_c6WmXt2id8U/R8HABBJjdjI/AAAAAAAAAHk/ZT_q6Ts53XY/s1600-h/components.png - Cabalisation is recent. In the past, we only had this hand-written (grr!) configure script plus a makefile. Now we have *that* and the Cabal stuff as a thin layer around this. The Cabal/Setup file is merely a thin wrapper around that and it is not clever enough to understand this '--user' flag (or something isn't being passed through; see http://hackage.haskell.org/trac/hackage/ticket/431 The good news is that we've made some progress: the wx package for example is cleanly Cabalised -- just the simple build method. In the darcs version of wxHaskell, I've also attempted to split wxcore off so that it is cleanly Cabalised (just the Simple build method), but I haven't worked out how to make it point the wxc package that we would have to build separately. Try it and see what I mean. I'm sure it's not a hard problem to solve; we just need somebody that's got 2 hours to stare at the problem, poke it in the right place. Can you help? My vague thinking is that this would somehow be a lot cleaner if we could tell people (i) go install wxWidgets (ii) go install wxC (iii) cabal install wx - There is a separate wxc project on sourceforge that tries to unify our, wxOCaml and wxEiffel's wxc work (all forks off wxEiffel, I think). We're now helping to administer the project, but again... nobody has the time to pay it attention. Argh! So very close to making it all work right! :-( Right now, my problem is that I don't really have the ability to give a clear description of the problem, that say Duncan (CC'ed) could understand and subsequently just give me an answer to. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
pgpAtR8dytfi3.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-users mailing list wxhaskell-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
