Re: [wxhaskell-devel] Build

2013-06-02 Thread harry
Eric Kow writes: > >PATH: (add these) > > %WXWIN%\lib\gcc_dll;%WXWIN%;%CABAL_DIR%\wxc-%WXC_VERSION%\%GHC_VERSION% > So by rights, as far as building wxHaskell and wxHaskell apps is concerned (sandbox or no), we need > “only” really set the WXWIN and WXCFG environment variables. I forget wha

Re: [wxhaskell-devel] Build

2013-06-02 Thread Eric Kow
On 2 Jun 2013, at 08:44, harry wrote: > Referring to the installation instructions, we have the following > environment variables: > >CABAL_DIR: C:\Users\XXX\AppData\Roaming\cabal (Windows XP: C:\Documents > and Settings\XXX\Application Data\cabal, or: %APPDATA%\cabal) >GHC_VERSION: 7.0.

Re: [wxhaskell-devel] Build

2013-06-02 Thread harry
Referring to the installation instructions, we have the following environment variables: CABAL_DIR: C:\Users\XXX\AppData\Roaming\cabal (Windows XP: C:\Documents and Settings\XXX\Application Data\cabal, or: %APPDATA%\cabal) GHC_VERSION: 7.0.3 (for our convenience) WXC_VERSION: 0.90.0.2

Re: [wxhaskell-devel] Build

2013-06-02 Thread Eric Kow
On 2 Jun 2013, at 07:56, harry wrote: > The next hurdle is wxcore, which expects to find various bits of wxc in > places that it should really be keeping its nose out of. I suspect that if > everything has been set up correctly outsides of the sandbox, this too will > succeed by following the envi