Re: [wxhaskell-devel] Build

2013-06-01 Thread harry
Eric Kow writes: > OK let me get this straight. Is the user-facing problem here that installing wxHaskell for use in a sandbox > environment is impossible or just very inconvenient/difficult? The problem is that cabal-dev tries to install all the dependencies automatically. So if I have a depen

Re: [wxhaskell-devel] Build

2013-06-01 Thread Howard B. Golden
On 06/01/2013 01:34 PM, Eric Kow wrote: > I had some longer comments on the technical issues. I think we may > be need to step back a bit and peel apart the fundamental issues > first (C++, shared libraries, other?) but first let's make sure we > understand what the user-facing problem really is.

Re: [wxhaskell-devel] Build

2013-06-01 Thread Eric Kow
OK, so let's step back a bit. I think Luc's right in two senses, first that we need to understand what the user-facing problem is, and second what is technical problem lying at the heart of user-facing problem. In your first message you said: > OTOH, cabal install wxdirect installs both the he

Re: [wxhaskell-devel] Build

2013-06-01 Thread harry
Eric Kow writes: > May I ask which environment variables in particular you're referring to? All of them, particularly those used to find the location of wxc. cabal-dev installs all dependencies blindly, and doesn't know to set environment variables. > (B) [an aspiring wxHaskell hacker] modify w