Hi Jeremy,
This build is not working for me, I'm afraid. It does a bunch of good stuff,
like:
parsing: src/eiffel/wxc_defs.e
parsing: src/eiffel/wx_defs.e
parsing: src/eiffel/stc.e
generating: src/haskell/Graphics/UI/WXCore/WxcDefs.hs
generated 2439 constant definitions
ok.
But then it dies with:
Please use the --prefix flag (as in wx-config --prefix=C:\wxWidgets)
or set the environment variable WXWIN (as in WXWIN=C:\wxWidgets)
to specify where is your installation of wxWidgets.
setup.exe: readProcess: wx-config "--libs" "--cppflags" (exit 1): failed
cabal.exe: Error: some packages failed to install:
wx-0.12.1.2 depends on wxcore-0.12.1.2 which failed to install.
wxcore-0.12.1.2 failed during the configure step. The exception was:
exit: ExitFailure 1
Well, I had set the WXWIN variable to /c/wxWidgets-2.8.10, so I don't know
why it would act like I hadn't. I also tried using the --prefix flag. I also
tried using a Windows-style path of C:\wxWidgets-2.8.10. None of this got
any different result.
Any ideas?
Thanks,
Lyle
On Fri, Nov 13, 2009 at 3:55 PM, Jeremy O'Donoghue <
jeremy.odonog...@gmail.com> wrote:
> Hi all,
>
> On behalf of the wxHaskell maintainers, I am very pleased to announce
> the release of wxHaskell 0.12.1.2.
>
> The key feature of this release is that it is now possible to install
> wxHaskell entirely using cabal on all targets (with a minor proviso on
> Windows). The credit for this achievement is almost all down to new
> contributor Brian Lewis, who has worked very hard to make this work
> 'just right', and given me (at least) an object lesson in how to use
> Cabal.
>
> The small proviso for Windows machines is that wxWidgets should be
> built using MSys - none of the other compilers supported by wxWidgets
> is currently working, but we consider this a small price to pay for
> the convenience of getting a GUI straight from cabal.
>
> For Unix machines which have wxWidgets 2.8.x installed, you should now
> be able to install wxHaskell with a simple:
>
> cabal install wx
>
> For Windows machines, there are a few prerequisites:
>
> 1) You will need the Windows port of wx-config in your path. This can
> be downloaded from http://wxconfig.googlepages.com/
> 2) You will need to compile wxWidgets using MSys. We have tested
> against MinGW 5.1.6 with g++ compiler, MinGW Make, MSYS-1.0.11,
> wxMSW-2.8.10, which are the latest versions, and can be downloaded
> from their respective websites. I used a completely clean install of
> the latest Haskell Platform to validate the procedure.
>
> Please note: all commands to be entered in an MSys shell.
>
> cd /c/path/to/wxWidgets-2.8.10/build/msw
> mingw32-make -f makefile.gcc BUILD=release MONOLITHIC=1 SHARED=1 UNICODE=1
>
> set PATH=$PATH:/c/path/to/wx-config
> set WXWIN=/c/path/to/wxWidgets-2.8.10
> set WXCFG=gcc_dll/mswu
> cabal install wx
>
> I will be updating the wxHaskell wiki to reflect these changes over
> the next day or so.
>
> Best Regards
> Jeremy O'Donoghue on behalf of the wxHaskell maintainers.
> _______________________________________________
> Haskell-Cafe mailing list
> haskell-c...@haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>
------------------------------------------------------------------------------
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
