wxhaskell-users — General mailing list for wxhaskell users

Re: [wxhaskell-users] Notes on installing wxHaskell on Mac OS Snow Leopard

[Conal E. <co...@co...>]

Worked for me. Thanks very much, Henry!  -- Conal

On Mon, Jul 2, 2012 at 6:31 PM, Henry Lockyer <hen...@nt...>wrote:

> Dear wxHaskell users / aspiring users,
>
> These are a few notes from getting a working 64bit installation of
> wxHaskell on Mac OS in case they are of any use to anyone.
>
> - This is for a 64-bit configuration starting from having 64-bit ghc 7.0.4
>  (HP 2011.4.0.0 64)
>
> - Mac os 10.6.8 snow leopard (with xcode 3.2.6)
>
> (This is not currently listed as a "known working configuration" at
> http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X )
>
> wxHaskell version issue:
> There is a linking problem with using the current wxc-0.90.0.3 and
> wxcore-0.90.0.1 from Hackage.
> They install ok but ghci throws a load of 'undefined symbols' when
> compiling from haskell using wxcore or wx .
> Thanks to Jeremy O'D. for identifying that the problem should disappear
> again in the latest development versions,
> which I got from:    https://github.com/jodonoghue/wxHaskell
>
> So the following installation was completed:
>
> 1. wxWidgets 2.9.3
> -----> installed globally (as dylib) in /usr/local...
>
> 2.  cabal-macosx-0.2.2  (cabal install from Hackage)
> 3.  wxdirect-0.90.0.1    (cabal install from Hackage)
> 4.  wxc-0.90.0.4           <===<<< Development version from Github
> 5.  wxcore-0.90.0.3       <===<<< Development version from Github
> 6.  wx-0.90.0.1            (cabal install from Hackage)
> (plus some additional dependency packages pulled in by cabal not shown)
>
>
> wxWidgets
> ========
> Stayed with wxWidgets 2.9.3 as being the current advertised 'stable'
> development release.
>
> 2.9 needed with wxHaskell 0.90 for 64bit.
>
> homebrew/macports may offer a convenient alternative approach to getting
> wxWidgets.
> I'm not familiar with these and don't have either installed so I just
> built wxWidgets myself as follows:
>
> Downloaded direct from http://wxWidgets.org/downloads/#latest_dev   page
> (tar.bz2) to a local
> user directory.
>
> Configure to avoid any potential problems that may arise from
> https://github.com/jodonoghue/wxHaskell/issues/2
> by temporarily editing out all inclusions of the QuickTime framework in
> the "configure" script file in the top level wxWidgets
> directory (only two places, simplest just to remove in both cases).
>
> - A response to a wxWidgets forum post suggested that the mac-related
> stuff is developing all the time and
>   advocated pulling the latest widgets development build, but I stuck to
> 2.9.3 in the interests of stability.
> - Another small potential advantage to taking the latest widgets
> development build may be getting changeset 71086
>    which aims to stop the inclusion of the QuickTime framework for
> i86_64-ONLY widgets builds.
>
> Mac Snow-Leopard evidently (usually) comes with wxWidgets 2.8
> pre-installed.
> I didn't want to alter the default Mac pre-installed stuff as far as
> possible, so adopted a configuration which left the
> 2.8 libraries installed and only disabled the 2.8 "wxrc" and "wx-config"
> executables in the path.
>
> If you want to check in advance for unlikely clashes with pre-existing
> stuff, then check /usr/local/lib where the dylib files
> "libwx_osx_cocoau_*"  and a "wx" directory will be placed.
> /usr/local/bin will get new "wx-config" and "wxrc*"
>
> Assuming my setup is standard,  wx-config for 2.8 should be found in the
> path at /usr/bin/wx-config and is a symlink to
> the main 2.8 stuff which is in /usr/lib so simply remove this link:
>  $ sudo rm -iv /usr/bin/wx-config
>
> There is also wxrc which is a link to wxrc-2.8 in the same directory, so
> remove the link but leave wxrc-2.8 there:
> $ sudo rm -iv /usr/bin/wxrc
>
> (These links can then simply re-created to re-instate path access to the
> 2.8 executables if wanted again in the future.)
>
> Create and cd to suitably named wxWidgets build subdirectory, then:
>
> $ ../configure --enable-macosx_arch=x86_64 --enable-unicode
> --disable-debug --with-osx_cocoa --enable-stc --enable-aui
> --enable-propgrid --enable-xrc --enable-ribbon --enable-richtext
> --enable-webkit --with-opengl
> +
> $ make
> +
> $ sudo make install
>
> (/usr/local is the default prefix in "configure")
>
> Check with command:
>
> $ wx-config --list
>
>     Default config is osx_cocoa-unicode-2.9
> ...
>
> $ wx-config --version
> 2.9.3
>
>
> Further checks:
>
> 1. cd to the wxWidgets samples and demos folders and "$ make" in each to
> check the samples and demos are working plausibly
>     (I found a couple of odd things but generally were working).
>
> 2. Build "minimal.cpp" from https://github.com/kowey/debug-wx
>
>
> wxHaskell
> ========
>
> Dependency chain wx -> wxcore -> wxc -> wxdirect
>
> Note: this is for a local user install.
>
> get master commit  Merge branch 'GHCI_FIX_BRANCH'<https://github.com/jodonoghue/wxHaskell/commit/1d6cff7be5b36032d85f068ea0266ec9da910298>
>   (at time of writing) eg. via CloneInMac
> at https://github.com/jodonoghue/wxHaskell
>
> wxdirect & cabal-macosx
> -----------------------------
>
> $ cabal install wxdirect cabal-macosx
>
> wxc
> -----
>
> cd to "wxc" folder of local copy from github
>
> The following configure parameters are based on
> http://www.haskell.org/haskellwiki/Mac_OS_X_Common_Installation_Paths
> but with an amendment to docdir to bring it in line with my local cabal
> config.
>
>
> $ runhaskell Setup configure --user
> --prefix=/Users/<YOURSELF>/Library/Haskell/ghc-7.0.4/lib/wxc-0.90.0.4
> --libsubdir= --datasubdir=
> --docdir=/Users/<YOURSELF>/Library/Haskell/ghc-7.0.4/lib/wxc-0.90.0.4/doc
> +
> $ runhaskell configure build
> +
> $ runhaskell configure install
>
> wxcore
> --------
>
> $ runhaskell Setup configure --user
> --prefix=/Users/<YOURSELF>/Library/Haskell/ghc-7.0.4/lib/wxcore-0.90.0.3
> --libsubdir= --datasubdir=
> --docdir=/Users/<YOURSELF>/Library/Haskell/ghc-7.0.4/lib/wxcore-0.90.0.3/doc
> +
> $ runhaskell configure build
> +
> $ runhaskell configure install
>
>
> checks
> --------
> Build wxcore "HelloWorld.hs" from https://github.com/kowey/debug-wx
> Wrap it with the macosx-app command.
> Enjoy.
>
> Note: It may start with the window positioned out of sight below left hand
> corner of the screen, don't miss it!
>
> wx
> ---
> This should have been a simple "cabal install wx" but for some strange
> reason I got:
>
>               src/Graphics/UI/WX/Draw.hs:33:8:
>                     Could not find module `Graphics.UI.WXCore':
>                           Perhaps you haven't installed the profiling
> libraries for package `wxcore-0.90.0.3'?
>                           Use -v to see a list of the files searched for.
>               cabal: Error: some packages failed to install:
>               wx-0.90.0.1 failed during the building phase. The exception
> was:
>               ExitFailure 1
>
>
> $ cabal install wx --disable-library-profiling
>
> ...seems to solve it.
>
> checks
> --------
> Build wx "HelloWorld.hs" from https://github.com/kowey/debug-wx
>
>
> Final Caveat
> =========
> I have so far only compiled and run simple 'helloworld' type programs
> using wxcore and wx, so not more widely tested yet.
>
>
> YMMV/ Henry
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>
>

[wxhaskell-users] Notes on installing wxHaskell on Mac OS Snow Leopard

[Henry L. <hen...@nt...>]

Dear wxHaskell users / aspiring users,

These are a few notes from getting a working 64bit installation of wxHaskell on Mac OS in case they are of any use to anyone.

- This is for a 64-bit configuration starting from having 64-bit ghc 7.0.4  (HP 2011.4.0.0 64) 

- Mac os 10.6.8 snow leopard (with xcode 3.2.6)

(This is not currently listed as a "known working configuration" at http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X )

wxHaskell version issue:
There is a linking problem with using the current wxc-0.90.0.3 and wxcore-0.90.0.1 from Hackage. 
They install ok but ghci throws a load of 'undefined symbols' when compiling from haskell using wxcore or wx .
Thanks to Jeremy O'D. for identifying that the problem should disappear again in the latest development versions,
which I got from:    https://github.com/jodonoghue/wxHaskell

So the following installation was completed:

1. wxWidgets 2.9.3      
-----> installed globally (as dylib) in /usr/local...

2.  cabal-macosx-0.2.2  (cabal install from Hackage)
3.  wxdirect-0.90.0.1    (cabal install from Hackage)
4.  wxc-0.90.0.4           <===<<< Development version from Github
5.  wxcore-0.90.0.3       <===<<< Development version from Github
6.  wx-0.90.0.1            (cabal install from Hackage)
(plus some additional dependency packages pulled in by cabal not shown) 
    

wxWidgets
========
Stayed with wxWidgets 2.9.3 as being the current advertised 'stable' development release. 

2.9 needed with wxHaskell 0.90 for 64bit.

homebrew/macports may offer a convenient alternative approach to getting wxWidgets.
I'm not familiar with these and don't have either installed so I just built wxWidgets myself as follows:

Downloaded direct from http://wxWidgets.org/downloads/#latest_dev   page (tar.bz2) to a local
user directory.

Configure to avoid any potential problems that may arise from  https://github.com/jodonoghue/wxHaskell/issues/2
by temporarily editing out all inclusions of the QuickTime framework in the "configure" script file in the top level wxWidgets
directory (only two places, simplest just to remove in both cases).
  
- A response to a wxWidgets forum post suggested that the mac-related stuff is developing all the time and
  advocated pulling the latest widgets development build, but I stuck to 2.9.3 in the interests of stability. 
- Another small potential advantage to taking the latest widgets development build may be getting changeset 71086 
   which aims to stop the inclusion of the QuickTime framework for i86_64-ONLY widgets builds. 

Mac Snow-Leopard evidently (usually) comes with wxWidgets 2.8 pre-installed.  
I didn't want to alter the default Mac pre-installed stuff as far as possible, so adopted a configuration which left the 
2.8 libraries installed and only disabled the 2.8 "wxrc" and "wx-config" executables in the path.

If you want to check in advance for unlikely clashes with pre-existing stuff, then check /usr/local/lib where the dylib files
"libwx_osx_cocoau_*"  and a "wx" directory will be placed.   /usr/local/bin will get new "wx-config" and "wxrc*"

Assuming my setup is standard,  wx-config for 2.8 should be found in the path at /usr/bin/wx-config and is a symlink to 
the main 2.8 stuff which is in /usr/lib so simply remove this link:      $ sudo rm -iv /usr/bin/wx-config

There is also wxrc which is a link to wxrc-2.8 in the same directory, so remove the link but leave wxrc-2.8 there:
$ sudo rm -iv /usr/bin/wxrc

(These links can then simply re-created to re-instate path access to the 2.8 executables if wanted again in the future.)

Create and cd to suitably named wxWidgets build subdirectory, then:

$ ../configure --enable-macosx_arch=x86_64 --enable-unicode --disable-debug --with-osx_cocoa --enable-stc --enable-aui --enable-propgrid --enable-xrc --enable-ribbon --enable-richtext --enable-webkit --with-opengl
+
$ make
+
$ sudo make install

(/usr/local is the default prefix in "configure")

Check with command:

$ wx-config --list

    Default config is osx_cocoa-unicode-2.9
...

$ wx-config --version
2.9.3


Further checks:

1. cd to the wxWidgets samples and demos folders and "$ make" in each to check the samples and demos are working plausibly 
    (I found a couple of odd things but generally were working).

2. Build "minimal.cpp" from https://github.com/kowey/debug-wx


wxHaskell
========

Dependency chain wx -> wxcore -> wxc -> wxdirect

Note: this is for a local user install.

get master commit  Merge branch 'GHCI_FIX_BRANCH'  (at time of writing) eg. via CloneInMac
at https://github.com/jodonoghue/wxHaskell

wxdirect & cabal-macosx
-----------------------------

$ cabal install wxdirect cabal-macosx

wxc
-----

cd to "wxc" folder of local copy from github

The following configure parameters are based on http://www.haskell.org/haskellwiki/Mac_OS_X_Common_Installation_Paths
but with an amendment to docdir to bring it in line with my local cabal config.


$ runhaskell Setup configure --user --prefix=/Users/<YOURSELF>/Library/Haskell/ghc-7.0.4/lib/wxc-0.90.0.4 --libsubdir= --datasubdir= --docdir=/Users/<YOURSELF>/Library/Haskell/ghc-7.0.4/lib/wxc-0.90.0.4/doc
+
$ runhaskell configure build
+
$ runhaskell configure install

wxcore
--------

$ runhaskell Setup configure --user --prefix=/Users/<YOURSELF>/Library/Haskell/ghc-7.0.4/lib/wxcore-0.90.0.3 --libsubdir= --datasubdir= --docdir=/Users/<YOURSELF>/Library/Haskell/ghc-7.0.4/lib/wxcore-0.90.0.3/doc
+
$ runhaskell configure build
+
$ runhaskell configure install


checks
--------
Build wxcore "HelloWorld.hs" from https://github.com/kowey/debug-wx
Wrap it with the macosx-app command.
Enjoy.

Note: It may start with the window positioned out of sight below left hand corner of the screen, don't miss it!

wx
---
This should have been a simple "cabal install wx" but for some strange reason I got:

              src/Graphics/UI/WX/Draw.hs:33:8:
                    Could not find module `Graphics.UI.WXCore':
                          Perhaps you haven't installed the profiling libraries for package `wxcore-0.90.0.3'?
                          Use -v to see a list of the files searched for.
              cabal: Error: some packages failed to install:
              wx-0.90.0.1 failed during the building phase. The exception was:
              ExitFailure 1


$ cabal install wx --disable-library-profiling

...seems to solve it.

checks
--------
Build wx "HelloWorld.hs" from https://github.com/kowey/debug-wx


Final Caveat
=========
I have so far only compiled and run simple 'helloworld' type programs using wxcore and wx, so not more widely tested yet.


YMMV/ Henry

[wxhaskell-users] wxHaskell 0.90 symbols not found

[Henry L. <hen...@nt...>]

Hi
Having got wxWidgets 2.9.3 built and installed satisfactorily, 
in i86_64-only configuration on Mac OS Snow Leopard (10.6.8) with GHC 7.0.4 (64bit HP ver.)

- widgets HelloWorld apps, demos and samples are building and executing OK at least -

I now try to get wxHaskell working but get the following messages when trying to 
compile/link either the wxcore HelloWorld from  
https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs
or the wx HelloWorld from 
https://github.com/kowey/debug-wx


Henrys-iMac:wxcore henrylockyer$ ghc HelloWorld.hs
[1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
Linking HelloWorld ...
Undefined symbols:
  "_wxListItemAttr_SetTextColour", referenced from:
      _s15xV_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_Create", referenced from:
      _sWbY_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _sWcg_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_GetBackgroundColor", referenced from:
      _s1Bis_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2Jgb_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrl_RefreshItem", referenced from:
      _s1C5g_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2HVB_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_SetOnGetItemAttrCallback", referenced from:
      _s1BFE_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2IEM_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_Create", referenced from:
      _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_SetOnGetItemColumnImageCallback", referenced from:
      _s1BE8_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2IGA_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_CreateEx", referenced from:
      _sUn6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _sUng_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_CreateWithCb", referenced from:
      _sW0i_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _sW0E_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrl_IsVirtual", referenced from:
      _s1C6N_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2HTp_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrl_GetItemFont", referenced from:
      _s1Cz0_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2H2z_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_SetFont", referenced from:
      _s15BK_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s15BO_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_SetOnGetItemImageCallback", referenced from:
      _s1BCC_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2IIo_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_GetTextColor", referenced from:
      _s1BfQ_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2JjR_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_GetFont", referenced from:
      _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_HasFont", referenced from:
      _s1Bdd_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2JnT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_SetBackgroundColour", referenced from:
      _s15Gu_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListCtrlVirtual_SetOnGetItemTextCallback", referenced from:
      _s1BB6_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2IKc_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_HasTextColour", referenced from:
      _s1BbT_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2Jq5_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
  "_wxListItemAttr_HasBackgroundColour", referenced from:
      _s1Bex_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
      _s2JlH_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
ld: symbol(s) not found
collect2: ld returned 1 exit status
Henrys-iMac:wxcore henrylockyer$ 


Any clues as to the problem here ?

Thanks/ Henry

[wxhaskell-users] static widgets?

[Henry L. <hen...@nt...>]

btw... does wxWidgets need to be a dynamically linked lib for some reason or will wxHaskell be equally happy with static?  
br/ Henry

Re: [wxhaskell-users] WxHaskell/Mac check

[Henry L. <hen...@nt...>]

Hi Jeremy + ALL

On 17 Jun 2012, at 11:55, Jeremy O'Donoghue wrote:

> Hi Henry,
> 
> On 14 June 2012 10:45, Henry Lockyer <hen...@nt...> wrote:
> . . .
> Installing wxHAskell 0.9 with wxWidgets 2.9.3 in Mac OS 10.6.8.
> . . .I am slightly reluctant to mess about with the original installed version if possible. . . 
> 
> The recommended approach to dealing with more than one wxWidgets install is to set the WXWIN environment variable to point to your preferred wxWidgets installation, and WX_CFG to point to the preferred build, e.g. WXWIN=/usr/local. You only need WX_CFG if you have e.g. debug and release build variants.

I must confess I didn't really understand how this should help, but I tried it anyway, and it does not seem to make any obvious difference. At least as I have done it. 

I set WXWIN to point to the root dir of my 2.9.3 build as instructed on http://wiki.wxwidgets.org/Setting_Environment_Variable_For_XCode as this is the only advice I could find wrt to using WXWIN on unix, though I suppose this is really to facilitate Xcode-based widgets-related development and not sure it's relevant.  I checked it was set (using "set") then reran the cabal install attempt, but I just get the same failure response.

As I see it, cabal install of wx etc. is using wx-config, which should not be the pre-installed one in /usr/bin (as highlighted in the WxHaskell/Mac wiki page) - or at least it should respond to confirm 2.9 is available ok in the place/s it knows about.  So when I previously tried simply putting my 2.9.3 lib dir as an additional lib path to cabal it did not work, and with or without this I always get the response below due to it finding the old 2.8 version.  So wx-config does not appear to take any notice of WXWIN. (or?)

"Configuring wxc-0.90.0.3...

  Warning: No config found to match: /usr/bin/wx-config --version=2.9 --version-full
           in /usr/lib/wx/config
  If you require this configuration, please install the desired
  library build.  If this is part of an automated configuration
  test and no other errors occur, you may safely ignore it.
  You may use wx-config --list to see all configs available in
  the default prefix.

setup: failed"

The wxWidgets online book, appendix B, does not suggest any 'standard' use of WXWIN on unix type systems.
"On Windows
After you’ve built wxWidgets, you should create an environment variable named WXWIN and set it to the home folder of your wxWidgets source tree. (If you use the command line to build, you can also set or override WXWIN at build time by passing it in as an option to your makefile.)
On Unix and Mac OS X
In a standard install, you need not do anything as long as wx-config is on your PATH. wx-config is all you need; see “Using wx-config” later in this appendix."     etc.

Looking at the wxwidgets wiki wx-config page I saw the brief comment:
On Unix systems, wx-config may be a symlink to specific wx-config files for various wxWidgets ports/platforms (wxbase-2.5-config, wxgtk-2.5-config, ...).
This is not terribly clear but I think it is suggesting that the wx-config in the path could be a symlink which you edit 'manually' to point to a different wx-config in another widgets directory when you want to change to use a different build (or set of builds) in another install location.  (Anyone got a better/different interpretation?)

I don't really understand the dylib linking process but I am supposing that wx-config is only implicated at link time, so it only needs to find the right wxWidgets at this time and things will continue to work afterwards once they are linked, regardless of where the wx-config and lib files were located  -  right????

Evidently wx-config will support multiple builds, but this seem to require them all to have been built in the same root widgets build location. 

So I plan to do something like the symlink idea, or I may just temporarily rename the old 2.8 wx-config and add my new local 2.9 directory to the end of the path list. This is the new plan, though it seems a bit messy.

Anyone out there see any problems with this ?

TIA / Henry

PS. I saw some interesting work around this topic in the wxHaskell-developers list in the thread 
eg. at http://www.mail-archive.com/wxh...@li.../msg00751.html  
for Lion, but it is beyond my current level of detail to be able to apply it, and I'm not sure if it is up to date or any of it is useable as-is. Frustratingly it seems to be addressing the QuickTime issue too! (though maybe it is just for 32bit, I forget) and there may even be a 'brew' including the changes. Unfortunately when I looked into homebrew I was put off using it as it wants to take over /usr/local (or at least it says using another directory is 'at your peril') and I have other stuff already sitting in there that I equally don't want to imperil (though the information about the level of peril seems conflicting). 

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Gregory G. <gu...@mu...>]

One additional step:

I was getting the error:
   The program can’t start because wxc.dll is missing from your computer.
   Try reinstalling the program to fix this problem.

So,   (From: http://wewantarock.wordpress.com/2012/04/18/wxhaskell-news/ )  
2. had to copy wxc.dll from ..\AppData\Roaming\cabal\wxc-0.90.0.2\ghc-7.0.4 to the current directory so that it could be found
3. had to add ..\wxWidgets2.9.3\lib\gcc_dll to the path so those DLLs could be found

-------------------------------------------
> -----Original Message-----
> Sent: Thursday, June 14, 2012 9:56 PM
> To: Fabian Binz; wxh...@li...
> Subject: RE: [wxhaskell-users] problems buiding wxHaskell on Windows
> 
> Hmm, I think I got it fixed.
> 
> I did a clean-out of cabal files, reloaded them all, and made sure that I only had wx-config
> 2.6 anywhere on my path, and it seems to build properly now!
> 
> I think that although I was seeing a new (2.6) wx-config, there was still an old (2.1) around on
> which was getting found somehow, and this was goofing things up. I deleted it, made sure only
> 2.6 versions were areound, and now it all seems to build.
> 
> Next to try in in Haskell!
> 
> Thanks for the help and hints.
> -------------------------------------------

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Gregory G. <gu...@mu...>]

Hmm, I think I got it fixed.

I did a clean-out of cabal files, reloaded them all, and made sure that I only had wx-config 2.6 anywhere on my path, and it seems to build properly now!

I think that although I was seeing a new (2.6) wx-config, there was still an old (2.1) around on which was getting found somehow, and this was goofing things up. I deleted it, made sure only 2.6 versions were areound, and now it all seems to build.

Next to try in in Haskell!

Thanks for the help and hints.
-------------------------------------------
> -----Original Message-----
> From: Gregory Guthrie [mailto:gu...@mu...]
> Sent: Thursday, June 14, 2012 7:52 PM
> To: Fabian Binz; wxh...@li...
> Subject: Re: [wxhaskell-users] problems buiding wxHaskell on Windows
> 
> C:\Users\guthrie>cabal --version
> cabal-install version 0.14.0
> using version 1.14.0 of the Cabal library
> 
> C:\Users\guthrie>ghc-pkg list
> E:/Plang/Haskell Platform\lib\package.conf.d:
>     Cabal-1.10.1.0
>     Cabal-1.10.2.0
>     Cabal-1.14.0
>    ...
> 
> C:\Users\guthrie>cabal install wxc
> Resolving dependencies...
> [1 of 1] Compiling Main             ( C:\Users\guthrie\AppData\Local\Temp\wxc-0.90.0.3-
> 12076\wxc-0.90.0.3\Setup.hs, C:\Users\guthrie\AppData
> \Local\Temp\wxc-0.90.0.3-12076\wxc-0.90.0.3\dist\setup\Main.o ) Linking
> C:\Users\guthrie\AppData\Local\Temp\wxc-0.90.0.3-12076\wxc-
> 0.90.0.3\dist\setup\setup.exe ...
> Configuring wxc-0.90.0.3...
> Configuring wxc to build against wxWidgets 2.9
> 
> setup.exe: Missing dependencies on foreign libraries:
> * Missing C libraries: wxmsw29ud_all, wxmsw29ud This problem can usually be solved by
> installing the system packages that provide these libraries (you may need the "-dev"
> versions). If the libraries are already installed but in a non-standard location then you can use
> the flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
> cabal: Error: some packages failed to install:
> wxc-0.90.0.3 failed during the configure step. The exception was:
> ExitFailure 1
> 
> 
> > -----Original Message-----
> > From: Fabian Binz [mailto:fab...@ya...]
> > Sent: Wednesday, June 13, 2012 1:02 PM
> > To: wxh...@li...
> > Subject: Re: [wxhaskell-users] problems buiding wxHaskell on Windows
> >
> > > But I note that the wiki page for wxHaskell says to have a
> > > cabal/wxc-xxx/ghcversion
> > I don't have that either. I thus conclude, that you don't need it and
> > it doesn't seem to be the source of your problem.
> >
> > > cabal install wxc
> > >  Resolving dependencies...
> > >  <command line>: cannot satisfy -package Cabal-1.10.2.0:
> >
> > Which version of Cabal (note: the library, not the tool cabal-install)
> > do you have installed? You can check that by running "ghc-pkg list" from the command line.
> > Maybe it's a problem with your package database (you can check by running "ghc-pkg check"
> > and if it is broken you can try "ghc-pkg recache").
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Gregory Guthrie [mailto:gu...@mu...]
> > Gesendet: Mittwoch, 13. Juni 2012 18:25
> > An: Fabian Binz; wxh...@li...
> > Betreff: RE: [wxhaskell-users] problems buiding wxHaskell on Windows
> >
> > Yes, I did just this. Using your flags all of wxWidgets compile, and all samples run.
> >
> > But I note that the wiki page for wxHaskell says to have a
> > cabal/wxc-xxx/ghcversion
> >
> > On the path, but I don't have any such directory in my cabal (although I did set the path...).
> > There is a wxdirect-0.90.0.1 installed there, nothing else new of "wx*".
> >
> > Trying to do the cabal installs, I used the version 21 of wx-config, and still get these
> errors:
> >
> >    E:\Plang\Libraries\wxWidgets2.9>cabal install wxc
> >    Resolving dependencies...
> >    [1 of 1] Compiling Main             ( C:\Users\guthrie\AppData\Local\Temp\wxc-0.
> >    90.0.3-11300\wxc-0.90.0.3\Setup.hs, C:\Users\guthrie\AppData\Local\Temp\wxc-
> 0.90
> >    .0.3-11300\wxc-0.90.0.3\dist\setup\Main.o )
> >    Linking C:\Users\guthrie\AppData\Local\Temp\wxc-0.90.0.3-11300\wxc-
> > 0.90.0.3\dist\setup\setup.exe ...
> >    Configuring wxc-0.90.0.3...
> >    Configuring wxc to build against wxWidgets 2.9
> >
> >    setup.exe: Missing dependencies on foreign libraries:
> >    * Missing C libraries: wxmsw29ud_all, wxmsw29ud
> >    This problem can usually be solved by installing the system packages that
> >    provide these libraries (you may need the "-dev" versions). If the libraries
> >    are already installed but in a non-standard location then you can use the
> >    flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
> >    cabal: Error: some packages failed to install:
> >    wxc-0.90.0.3 failed during the configure step. The exception was:
> >    ExitFailure 1
> >
> > Using your FLAGS did help in the build of wxWidgets, now all of the samples compile and
> run.
> >
> > Upgrading to version 26 of wx-config changes the errors to this:
> >
> >    C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install wxc
> >    Resolving dependencies...
> >    <command line>: cannot satisfy -package Cabal-1.10.2.0:
> >     Cabal-1.10.2.0-db589dd5d526d3111ac2fde0f9ab986c is unusable due to missing or
> recursive dependencies:
> >       array-0.3.0.2-8e9cd0144e87fa9cc86cc9031631c4f3 base-4.3.1.0-f520cd232cc386
> >    346843c4a12b63f44b containers-0.4.0.0-18deac99a132f04751d862b77aab136e
> directory
> >    -1.1.0.0-3a2367d72569467a8af8a231656ff1b8 filepath-1.2.0.0-
> f132e9f7703da4e20a47f
> >    f2b9acf1ea1 old-time-1.0.0.6-445ce39cbcebd38069c25c0f383b728d pretty-1.0.1.2-abc
> >    7c632374e50e1c1927987c2651f0f process-1.0.1.5-
> > b3dded8e54a2e13d22af410bdcfafff4
> >        (use -v for more information)
> >    cabal: Error: some packages failed to install:
> >    wxc-0.90.0.3 failed during the configure step. The exception was:
> >    ExitFailure 1
> >
> > Trying to resolve them:
> >    C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install base
> >    Resolving dependencies...
> >    cabal: internal error: impossible
> >
> >    C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install array
> >    Resolving dependencies...
> >    No packages to be installed. All the requested packages are already installed.
> >    If you want to reinstall anyway then use the --reinstall flag.
> >
> >    C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install process
> >    Resolving dependencies...
> >    No packages to be installed. All the requested packages are already installed.
> >    If you want to reinstall anyway then use the --reinstall flag.
> >
> > Etc...  ???
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and threat landscape has changed
> and how IT managers can respond. Discussions will include endpoint security, mobile security
> and the latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Gregory G. <gu...@mu...>]

C:\Users\guthrie>cabal --version
cabal-install version 0.14.0
using version 1.14.0 of the Cabal library

C:\Users\guthrie>ghc-pkg list
E:/Plang/Haskell Platform\lib\package.conf.d:
    Cabal-1.10.1.0
    Cabal-1.10.2.0
    Cabal-1.14.0
   ...

C:\Users\guthrie>cabal install wxc
Resolving dependencies...
[1 of 1] Compiling Main             ( C:\Users\guthrie\AppData\Local\Temp\wxc-0.90.0.3-12076\wxc-0.90.0.3\Setup.hs, C:\Users\guthrie\AppData
\Local\Temp\wxc-0.90.0.3-12076\wxc-0.90.0.3\dist\setup\Main.o )
Linking C:\Users\guthrie\AppData\Local\Temp\wxc-0.90.0.3-12076\wxc-0.90.0.3\dist\setup\setup.exe ...
Configuring wxc-0.90.0.3...
Configuring wxc to build against wxWidgets 2.9

setup.exe: Missing dependencies on foreign libraries:
* Missing C libraries: wxmsw29ud_all, wxmsw29ud
This problem can usually be solved by installing the system packages that
provide these libraries (you may need the "-dev" versions). If the libraries
are already installed but in a non-standard location then you can use the
flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
cabal: Error: some packages failed to install:
wxc-0.90.0.3 failed during the configure step. The exception was:
ExitFailure 1


> -----Original Message-----
> From: Fabian Binz [mailto:fab...@ya...]
> Sent: Wednesday, June 13, 2012 1:02 PM
> To: wxh...@li...
> Subject: Re: [wxhaskell-users] problems buiding wxHaskell on Windows
> 
> > But I note that the wiki page for wxHaskell says to have a cabal/wxc-xxx/ghcversion
> I don't have that either. I thus conclude, that you don't need it and it doesn't seem to be
> the source of your problem.
> 
> > cabal install wxc
> >  Resolving dependencies...
> >  <command line>: cannot satisfy -package Cabal-1.10.2.0:
> 
> Which version of Cabal (note: the library, not the tool cabal-install) do you have installed? You
> can check that by running "ghc-pkg list" from the command line.
> Maybe it's a problem with your package database (you can check by running "ghc-pkg check"
> and if it is broken you can try "ghc-pkg recache").
> 
> -----Ursprüngliche Nachricht-----
> Von: Gregory Guthrie [mailto:gu...@mu...]
> Gesendet: Mittwoch, 13. Juni 2012 18:25
> An: Fabian Binz; wxh...@li...
> Betreff: RE: [wxhaskell-users] problems buiding wxHaskell on Windows
> 
> Yes, I did just this. Using your flags all of wxWidgets compile, and all samples run.
> 
> But I note that the wiki page for wxHaskell says to have a cabal/wxc-xxx/ghcversion
> 
> On the path, but I don't have any such directory in my cabal (although I did set the path...).
> There is a wxdirect-0.90.0.1 installed there, nothing else new of "wx*".
> 
> Trying to do the cabal installs, I used the version 21 of wx-config, and still get these errors:
> 
>    E:\Plang\Libraries\wxWidgets2.9>cabal install wxc
>    Resolving dependencies...
>    [1 of 1] Compiling Main             ( C:\Users\guthrie\AppData\Local\Temp\wxc-0.
>    90.0.3-11300\wxc-0.90.0.3\Setup.hs, C:\Users\guthrie\AppData\Local\Temp\wxc-0.90
>    .0.3-11300\wxc-0.90.0.3\dist\setup\Main.o )
>    Linking C:\Users\guthrie\AppData\Local\Temp\wxc-0.90.0.3-11300\wxc-
> 0.90.0.3\dist\setup\setup.exe ...
>    Configuring wxc-0.90.0.3...
>    Configuring wxc to build against wxWidgets 2.9
> 
>    setup.exe: Missing dependencies on foreign libraries:
>    * Missing C libraries: wxmsw29ud_all, wxmsw29ud
>    This problem can usually be solved by installing the system packages that
>    provide these libraries (you may need the "-dev" versions). If the libraries
>    are already installed but in a non-standard location then you can use the
>    flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
>    cabal: Error: some packages failed to install:
>    wxc-0.90.0.3 failed during the configure step. The exception was:
>    ExitFailure 1
> 
> Using your FLAGS did help in the build of wxWidgets, now all of the samples compile and run.
> 
> Upgrading to version 26 of wx-config changes the errors to this:
> 
>    C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install wxc
>    Resolving dependencies...
>    <command line>: cannot satisfy -package Cabal-1.10.2.0:
>     Cabal-1.10.2.0-db589dd5d526d3111ac2fde0f9ab986c is unusable due to missing or recursive dependencies:
>       array-0.3.0.2-8e9cd0144e87fa9cc86cc9031631c4f3 base-4.3.1.0-f520cd232cc386
>    346843c4a12b63f44b containers-0.4.0.0-18deac99a132f04751d862b77aab136e directory
>    -1.1.0.0-3a2367d72569467a8af8a231656ff1b8 filepath-1.2.0.0-f132e9f7703da4e20a47f
>    f2b9acf1ea1 old-time-1.0.0.6-445ce39cbcebd38069c25c0f383b728d pretty-1.0.1.2-abc
>    7c632374e50e1c1927987c2651f0f process-1.0.1.5-
> b3dded8e54a2e13d22af410bdcfafff4
>        (use -v for more information)
>    cabal: Error: some packages failed to install:
>    wxc-0.90.0.3 failed during the configure step. The exception was:
>    ExitFailure 1
> 
> Trying to resolve them:
>    C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install base
>    Resolving dependencies...
>    cabal: internal error: impossible
> 
>    C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install array
>    Resolving dependencies...
>    No packages to be installed. All the requested packages are already installed.
>    If you want to reinstall anyway then use the --reinstall flag.
> 
>    C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install process
>    Resolving dependencies...
>    No packages to be installed. All the requested packages are already installed.
>    If you want to reinstall anyway then use the --reinstall flag.
> 
> Etc...  ???

[wxhaskell-users] Setup failed

[Henning T. <le...@he...>]

On a Linux machine that I do not administrate the configuration of 
wxcore-0.13.2 stopped with a simple "Setup failed" and also the verbose 
mode did not show more information.

Then I found out that the package wx2.8-headers was installed but the 
package libwxgtk2.8-dev was missing. After libwxgtk2.8-dev was installed 
the package could be compiled and installed.

[wxhaskell-users] WxHaskell/Mac check

[Henry L. <hen...@nt...>]

To hopefully avoid an unnecessary detour today:

Installing wxHAskell 0.9 with wxWidgets 2.9.3 in Mac OS 10.6.8.

Before I build and install the wxWidgets lib locally:

I note the WxHAskell/Mac instructions (in step 3) insist the older pre-installed widgets should not be found in /usr/bin,
and the proposed configuration parameters (in step 2) put the widgets in /usr/local/, but I am slightly reluctant to mess
about with the original installed version if possible.

Is the wx install indiscriminate in its choice of widgets library version, and will just try to go with the first one it finds, 
or will it search for an appropriate compatible version?  

I was hoping to either do something like
 cabal install wx cabal-macosx --extra-lib-dirs=<PATH TO MY LOCAL WIDGETS 2.9 LIB DIR>

OR to add the local widgets lib dir onto $PATH  (in paths.d for example) where it would be searched
after /usr/bin (I believe).   (+ I presume this is also what would happen if I just installed in /usr/local as
per the instructions, without also removing the old widgets, 
and presumably 'which wx-config' will still find the old one first in this case) 

Will this approach  not/work OK?

TIA / Henry

Re: [wxhaskell-users] Can't link my app with wxHaskell-0.90.0.1 on Lion

[Colin M. <col...@ta...>]

On 22/05/2012 10:23, Jeremy O'Donoghue wrote:
> Hi Hiratara,
>...
>     I want to compile a sample program which uses wxHaskell
>     on Mac OS X Lion, but I couldn't build it.
>
>     I compiled HelloWorld.hs and I got following linker errors.
> ...
>     "_wxListItemAttr_GetFont", referenced from:
>           _s1Bh9_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
>           _s2Ji1_info in libHSwxcore-0.90.0.1.a(WxcClassesAL.o)
> ...
>
> I need to check, but this looks as though you have a version of wxc
> which is incompatible with the wxcore you have. This is almost probably
> my fault (incorrect dependencies), and nothing to do with you - the
> install steps you have taken look correct to me.
>
> I will check whether I see the same problem on a clean install of
> wxHaskell, and upload a new version if needed.
>
Has there been any further progress on this issue?  I too am seeing 
these link errors.  In my case I installed wxWidgets via macports 
(wxWidgets-devel @2.9.3) and specified a universal build.

Regards,
-- CMcP

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Fabian B. <fab...@ya...>]

> But I note that the wiki page for wxHaskell says to have a cabal/wxc-xxx/ghcversion
I don't have that either. I thus conclude, that you don't need it and it doesn't seem to be the source of your problem.

> cabal install wxc
>  Resolving dependencies...
>  <command line>: cannot satisfy -package Cabal-1.10.2.0:

Which version of Cabal (note: the library, not the tool cabal-install) do you have installed? You can check that by running "ghc-pkg list" from the command line.
Maybe it's a problem with your package database (you can check by running "ghc-pkg check" and if it is broken you can try "ghc-pkg recache").

-----Ursprüngliche Nachricht-----
Von: Gregory Guthrie [mailto:gu...@mu...] 
Gesendet: Mittwoch, 13. Juni 2012 18:25
An: Fabian Binz; wxh...@li...
Betreff: RE: [wxhaskell-users] problems buiding wxHaskell on Windows

Yes, I did just this. Using your flags all of wxWidgets compile, and all samples run.

But I note that the wiki page for wxHaskell says to have a cabal/wxc-xxx/ghcversion

On the path, but I don't have any such directory in my cabal (although I did set the path...).
There is a wxdirect-0.90.0.1 installed there, nothing else new of "wx*".

Trying to do the cabal installs, I used the version 21 of wx-config, and still get these errors:

   E:\Plang\Libraries\wxWidgets2.9>cabal install wxc
   Resolving dependencies...
   [1 of 1] Compiling Main             ( C:\Users\guthrie\AppData\Local\Temp\wxc-0.
   90.0.3-11300\wxc-0.90.0.3\Setup.hs, C:\Users\guthrie\AppData\Local\Temp\wxc-0.90
   .0.3-11300\wxc-0.90.0.3\dist\setup\Main.o )
   Linking C:\Users\guthrie\AppData\Local\Temp\wxc-0.90.0.3-11300\wxc-0.90.0.3\dist\setup\setup.exe ...
   Configuring wxc-0.90.0.3...
   Configuring wxc to build against wxWidgets 2.9

   setup.exe: Missing dependencies on foreign libraries:
   * Missing C libraries: wxmsw29ud_all, wxmsw29ud
   This problem can usually be solved by installing the system packages that
   provide these libraries (you may need the "-dev" versions). If the libraries
   are already installed but in a non-standard location then you can use the
   flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
   cabal: Error: some packages failed to install:
   wxc-0.90.0.3 failed during the configure step. The exception was:
   ExitFailure 1

Using your FLAGS did help in the build of wxWidgets, now all of the samples compile and run.

Upgrading to version 26 of wx-config changes the errors to this:

   C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install wxc
   Resolving dependencies...
   <command line>: cannot satisfy -package Cabal-1.10.2.0:
    Cabal-1.10.2.0-db589dd5d526d3111ac2fde0f9ab986c is unusable due to missing or recursive dependencies:
      array-0.3.0.2-8e9cd0144e87fa9cc86cc9031631c4f3 base-4.3.1.0-f520cd232cc386
   346843c4a12b63f44b containers-0.4.0.0-18deac99a132f04751d862b77aab136e directory
   -1.1.0.0-3a2367d72569467a8af8a231656ff1b8 filepath-1.2.0.0-f132e9f7703da4e20a47f
   f2b9acf1ea1 old-time-1.0.0.6-445ce39cbcebd38069c25c0f383b728d pretty-1.0.1.2-abc
   7c632374e50e1c1927987c2651f0f process-1.0.1.5-b3dded8e54a2e13d22af410bdcfafff4
       (use -v for more information)
   cabal: Error: some packages failed to install:
   wxc-0.90.0.3 failed during the configure step. The exception was:
   ExitFailure 1

Trying to resolve them:
   C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install base
   Resolving dependencies...
   cabal: internal error: impossible

   C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install array
   Resolving dependencies...
   No packages to be installed. All the requested packages are already installed.
   If you want to reinstall anyway then use the --reinstall flag.

   C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install process
   Resolving dependencies...
   No packages to be installed. All the requested packages are already installed.
   If you want to reinstall anyway then use the --reinstall flag.

Etc...  ???
-------------------------------------------
> -----Original Message-----
> From: Fabian Binz [mailto:fab...@ya...]
> Sent: Thursday, June 07, 2012 12:37 PM
> To: wxh...@li...
> Subject: Re: [wxhaskell-users] problems buiding wxHaskell on Windows
> 
> > Does anyone run WxHaskell 2.9 on Windows?
> Yes.
> 
> > library files: gcc_mswuddll & gcc_mswudll
> It should create a wxmsw293u_gcc_custom.dll (and maybe a 
> wxmsw293u_gl_gcc_custom.dll for OpenGL support).
> 
> Do you run "cabal install wxc" from Msys-Bash or from cmd.exe? You should use the latter.
> Also, which make flags did you use? I compiled wxWidgets-2.9.3 with 
> the following command (from msys-bash):
> 
> cd your-wxWidgets-2.9.3-dir/build/msw
> mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1
> 
> Then, with the wx-config.exe from the wiki page in PATH, I open cmd.exe and type:
> cabal install wxc
> 
> I hope this helps.
> 
> Regards,
> Fabian
> 

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Gregory G. <gu...@mu...>]

Yes, I did just this. Using your flags all of wxWidgets compile, and all samples run.

But I note that the wiki page for wxHaskell says to have a cabal/wxc-xxx/ghcversion

On the path, but I don't have any such directory in my cabal (although I did set the path...).
There is a wxdirect-0.90.0.1 installed there, nothing else new of "wx*".

Trying to do the cabal installs, I used the version 21 of wx-config, and still get these errors:

   E:\Plang\Libraries\wxWidgets2.9>cabal install wxc
   Resolving dependencies...
   [1 of 1] Compiling Main             ( C:\Users\guthrie\AppData\Local\Temp\wxc-0.
   90.0.3-11300\wxc-0.90.0.3\Setup.hs, C:\Users\guthrie\AppData\Local\Temp\wxc-0.90
   .0.3-11300\wxc-0.90.0.3\dist\setup\Main.o )
   Linking C:\Users\guthrie\AppData\Local\Temp\wxc-0.90.0.3-11300\wxc-0.90.0.3\dist\setup\setup.exe ...
   Configuring wxc-0.90.0.3...
   Configuring wxc to build against wxWidgets 2.9

   setup.exe: Missing dependencies on foreign libraries:
   * Missing C libraries: wxmsw29ud_all, wxmsw29ud
   This problem can usually be solved by installing the system packages that
   provide these libraries (you may need the "-dev" versions). If the libraries
   are already installed but in a non-standard location then you can use the
   flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
   cabal: Error: some packages failed to install:
   wxc-0.90.0.3 failed during the configure step. The exception was:
   ExitFailure 1

Using your FLAGS did help in the build of wxWidgets, now all of the samples compile and run.

Upgrading to version 26 of wx-config changes the errors to this:

   C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install wxc
   Resolving dependencies...
   <command line>: cannot satisfy -package Cabal-1.10.2.0:
    Cabal-1.10.2.0-db589dd5d526d3111ac2fde0f9ab986c is unusable due to missing or recursive dependencies:
      array-0.3.0.2-8e9cd0144e87fa9cc86cc9031631c4f3 base-4.3.1.0-f520cd232cc386
   346843c4a12b63f44b containers-0.4.0.0-18deac99a132f04751d862b77aab136e directory
   -1.1.0.0-3a2367d72569467a8af8a231656ff1b8 filepath-1.2.0.0-f132e9f7703da4e20a47f
   f2b9acf1ea1 old-time-1.0.0.6-445ce39cbcebd38069c25c0f383b728d pretty-1.0.1.2-abc
   7c632374e50e1c1927987c2651f0f process-1.0.1.5-b3dded8e54a2e13d22af410bdcfafff4
       (use -v for more information)
   cabal: Error: some packages failed to install:
   wxc-0.90.0.3 failed during the configure step. The exception was:
   ExitFailure 1

Trying to resolve them:
   C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install base
   Resolving dependencies...
   cabal: internal error: impossible

   C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install array
   Resolving dependencies...
   No packages to be installed. All the requested packages are already installed.
   If you want to reinstall anyway then use the --reinstall flag.

   C:\Users\guthrie\AppData\Roaming\cabal\bin>cabal install process
   Resolving dependencies...
   No packages to be installed. All the requested packages are already installed.
   If you want to reinstall anyway then use the --reinstall flag.

Etc...  ???
-------------------------------------------
> -----Original Message-----
> From: Fabian Binz [mailto:fab...@ya...]
> Sent: Thursday, June 07, 2012 12:37 PM
> To: wxh...@li...
> Subject: Re: [wxhaskell-users] problems buiding wxHaskell on Windows
> 
> > Does anyone run WxHaskell 2.9 on Windows?
> Yes.
> 
> > library files: gcc_mswuddll & gcc_mswudll
> It should create a wxmsw293u_gcc_custom.dll (and maybe a wxmsw293u_gl_gcc_custom.dll
> for OpenGL support).
> 
> Do you run "cabal install wxc" from Msys-Bash or from cmd.exe? You should use the latter.
> Also, which make flags did you use? I compiled wxWidgets-2.9.3 with the following command
> (from msys-bash):
> 
> cd your-wxWidgets-2.9.3-dir/build/msw
> mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1
> 
> Then, with the wx-config.exe from the wiki page in PATH, I open cmd.exe and type:
> cabal install wxc
> 
> I hope this helps.
> 
> Regards,
> Fabian
> 

Re: [wxhaskell-users] mac OS installation help sought

[Henry L. <hen...@nt...>]

Hi Eric
Thanks a lot for the responses.

On 11 Jun 2012, at 09:20, Eric Kow wrote:
> Have you considered adopting some sort of package management/installation software like Homebrew or MacPorts?
> It could make life a lot easier than trying to build things by hand.

I will take a look.. I did consider it (and others recommended it) but having already forced myself to step into the cold water 
and try and figure out some of this basic unixy stuff I thought I may as well stay on one track, and had reached the point 
over this last week where building the wxWidgets package itself now seemed quite familiar at least  ;-) 
It's pretty easy with the wxWidgets configuration tool, albeit it takes a bit of time for it to make it all.

>> I then saw Unresolved QuickTime dependency on Mac OS X? on github and remembered I had received:
>> "ld: warning: in /System/Library/Frameworks//QuickTime.framework/QuickTime, missing required architecture x86_64 in file"
>> In fact this warning is repeated throughout the terminal output. It seems to occur every time there is a g++ command that 
>> (just a guess at this point) is linking the 2.9.3 widgets lib (has parameter "-L/Users/henrylockyer/wxWidgets/wxWidgets-2.9.3/build-cocoa-debug/lib", 
>> and also has the param "-framework QuickTime" ).
> 
> I just tend to shrug and ignore the issue myself (using a 64 bit GHC)

Are you running 64 bit with wxHaskell on Snow Leopard ?

I initially saw it as 'just a warning' and was going to ignore it but Conal Elliot who raised the above problem report seemed to be trying
to run the same setup as I was and it seemed to be causing a fairly basic breakdown. (*Presumably* 64 bit HP)
I also noted that on the wxHaskell/Mac page the "known to be working configurations" list only mentions 32 bit with Snow Leopard.
Hence my question:

>> I chose the 64 bit GHC option, so would I need to go back and reload this in 32 bit form?

I did not completely understand Heinrich Apfelmus' suggested solution to the above problem: why go for universal binary widgets 
if you just want to change over to a 32bit solution (including GHC) ?
But I supposed this might be more to do with macports (?). Maybe there is not a convenient 32-bit only version on macports, but just guessing.

(I also posted a little of the results of my own playing with trying to build a 64-bit widgets without QuickTime framework at
https://github.com/jodonoghue/wxHaskell/issues/2 )

>> Before I started the install attempt I was also a little unclear from reading the 
>> page at http://www.haskell.org/haskellwiki/WxHaskell  says ver. 2.8.x is easiest to get working, 
>> but the "Building and Installing / MacOS X" linked page at http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X
>> only talks about wxWidgets version 2.9, implying wxHaskell 0.9, no mention of 0.13, so I went with 0.9.   
>> Is wxHaskell 0.13 also ok for MacOS X?  Would this be better? 
> 
> I think the basic story is that  wxHaskell 0.13 is easier for Windows, and 0.90 for Mac. You need it for 64 bit GHC, and it works fine with 32 bit, so rather than struggle to correctly maintain two sets of install instructions, we just went with the latter.
> 

OK. That gives some encouragement to stay with 0.90 ! 

Regards/ Henry

Re: [wxhaskell-users] mac OS installation help sought

[Eric K. <eri...@gm...>]

Hi Henry,

Picking and choosing some easy questions to answer
(I've very slightly updated http://www.haskell.org/haskellwiki/WxHaskell/Mac too)

On 5 Jun 2012, at 02:52, Henry Lockyer wrote:
> Hopefully appropriate to ask for basic help on this list (?)

Just the right place for this sort of question.

It's helpful to use Gmane for searching rather than trying to puzzle through the SF archive page, I find.

> It's for MacOS X 10.6.8 (Snow Leopard). 
> 
> I just upgraded GHC to 7.0.4, 64-bit option.

Have you considered adopting some sort of package management/installation software like Homebrew or MacPorts?

It could make life a lot easier than trying to build things by hand.

> (So, no attempt to install wxHaskell itself yet.)
> 
> I then saw Unresolved QuickTime dependency on Mac OS X? on github and remembered I had received:
> "ld: warning: in /System/Library/Frameworks//QuickTime.framework/QuickTime, missing required architecture x86_64 in file"
> In fact this warning is repeated throughout the terminal output. It seems to occur every time there is a g++ command that 
> (just a guess at this point) is linking the 2.9.3 widgets lib (has parameter "-L/Users/henrylockyer/wxWidgets/wxWidgets-2.9.3/build-cocoa-debug/lib", 
> and also has the param "-framework QuickTime" ).

I just tend to shrug and ignore the issue myself (using a 64 bit GHC)

> I chose the 64 bit GHC option, so would I need to go back and reload this in 32 bit form?
> 
> Before I started the install attempt I was also a little unclear from reading the 
> page at http://www.haskell.org/haskellwiki/WxHaskell  says ver. 2.8.x is easiest to get working, 
> but the "Building and Installing / MacOS X" linked page at http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X
> only talks about wxWidgets version 2.9, implying wxHaskell 0.9, no mention of 0.13, so I went with 0.9.   
> Is wxHaskell 0.13 also ok for MacOS X?  Would this be better? 

I think the basic story is that  wxHaskell 0.13 is easier for Windows, and 0.90 for Mac. You need it for 64 bit GHC, and it works fine with 32 bit, so rather than struggle to correctly maintain two sets of install instructions, we just went with the latter.

-- 
Eric Kow <http://erickow.com>

Re: [wxhaskell-users] Running out of memory, installing wxcore

[Henk-Jan v. T. <hj...@ch...>]

On Thu, 07 Jun 2012 22:19:04 +0200, Henk-Jan van Tuyl <hj...@ch...>  
wrote:

>
> L.S.,
>
> Using my patched version of wxcore (see my previous e-mail), my system
> (Windows XP) runs out of memory (1 GiB real, 4 GiB virtual), when trying
> to install wxcore. See the session below.

OK, I've found the problem; my patch was wrong. Moving on to the next  
problem.

Regards,
Henk-Jan van Tuyl


-- 
http://Van.Tuyl.eu/
http://members.chello.nl/hjgtuyl/tourdemonad.html
Haskell programming
--

[wxhaskell-users] Running out of memory, installing wxcore

[Henk-Jan v. T. <hj...@ch...>]

L.S.,

Using my patched version of wxcore (see my previous e-mail), my system  
(Windows XP) runs out of memory (1 GiB real, 4 GiB virtual), when trying  
to install wxcore. See the session below.

C:\Haskell\Temp\wxcore-0.90.0.1>cabal install
Resolving dependencies...
Configuring wxcore-0.90.0.1...
Generating class type definitions from .h files
setup.exe: out of memory
cabal: Error: some packages failed to install:
wxcore-0.90.0.1 failed during the configure step. The exception was:
ExitFailure 1


Does anyone have the same experience? Any quick solution?

Regards,
Henk-Jan van Tuyl


-- 
http://Van.Tuyl.eu/
http://members.chello.nl/hjgtuyl/tourdemonad.html
Haskell programming
--

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Fabian B. <fab...@ya...>]

> Does anyone run WxHaskell 2.9 on Windows?
Yes.

> library files: gcc_mswuddll & gcc_mswudll
It should create a wxmsw293u_gcc_custom.dll (and maybe a wxmsw293u_gl_gcc_custom.dll for OpenGL support).

Do you run "cabal install wxc" from Msys-Bash or from cmd.exe? You should use the latter.
Also, which make flags did you use? I compiled wxWidgets-2.9.3 with the following command (from msys-bash):

cd your-wxWidgets-2.9.3-dir/build/msw
mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 

Then, with the wx-config.exe from the wiki page in PATH, I open cmd.exe and type:
cabal install wxc

I hope this helps.

Regards, 
Fabian

-----Ursprüngliche Nachricht-----
Von: Gregory Guthrie [mailto:gu...@mu...] 
Gesendet: Donnerstag, 7. Juni 2012 18:12
An: David Virebayre
Cc: wxh...@li...
Betreff: Re: [wxhaskell-users] problems buiding wxHaskell on Windows

I did a complete re-build of wxWidgets2.9, and it seemed to complete successfully with a built library files: gcc_mswuddll & gcc_mswudll.

Then I went into the samples directory and built all the samples, they all seemed to build fine, but when I try to execute them they give:
"   wbase293ud_gcc_custom.dll not found ...".

And it still doesn't seem to have installed wxc or wxcore (not in the cabal directory).

Does anyone run WxHaskell 2.9 on Windows?
––––––––––––––––––––––––––––––––––––––––––––––––
> Cc: wxh...@li...
> Subject: Re: [wxhaskell-users] problems buiding wxHaskell on Windows
>
> I've never managed to get wxHaskell running without problems on windows, last time I tried there was some kind of encoding problem, and I gave up.
>
>That would be cool if there was an installer that would install wxHaskell with all dependences on top of a freshly installed haskell platform on windows.
>
>I would be eternally thankful if someone could do that.
>
> David.


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
wxhaskell-users mailing list
wxh...@li...
https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Gregory G. <gu...@mu...>]

I did a complete re-build of wxWidgets2.9, and it seemed to complete successfully with a built library files: gcc_mswuddll & gcc_mswudll.

Then I went into the samples directory and built all the samples, they all seemed to build fine, but when I try to execute them they give:
"   wbase293ud_gcc_custom.dll not found ...".

And it still doesn't seem to have installed wxc or wxcore (not in the cabal directory).

Does anyone run WxHaskell 2.9 on Windows?
––––––––––––––––––––––––––––––––––––––––––––––––
> Cc: wxh...@li...
> Subject: Re: [wxhaskell-users] problems buiding wxHaskell on Windows
>
> I've never managed to get wxHaskell running without problems on windows, last time I tried there was some kind of encoding problem, and I gave up.
>
>That would be cool if there was an installer that would install wxHaskell with all dependences on top of a freshly installed haskell platform on windows.
>
>I would be eternally thankful if someone could do that. 
>
> David.

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Heinrich A. <apf...@qu...>]

Antton Tapani wrote:
> Installer would indeed be very nice, but it takes a lot of work to
> create and maintain universal installer and it would currently benefit
> only a handful of  people. I'm guessing the majority of wxhaskell
> users are fairly savvy developers, so it would not seem worth the
> trouble. That of course quickly becomes self fulfilling statement
> since it will actively drive away people who have no interest in
> fiddling with the nuances of the installation process. They may give
> it a try, but fail and give up and you never hear from them.
> 
> I will devote some time on this if I end up using haskell on more
> projects. Most people who wish to use wxhaskell are not likely to
> participate in its development, but at the same time people are less
> willing to develop a library with only few users. Haskell platform
> itself is pretty much single click installation, and it is very easy
> to get started with. Ideally that should be the case with every gui
> toolkit as well.

[Cross posting to the libraries list.]

Actually, maybe it's possible to integrate the creation of one-click 
installers with the Haskell Platform efforts?

The best option would be to have wxHaskell to become part of the 
platform, but it probably doesn't meet the criteria for inclusion right 
now. But the focus is on the underlying C libraries anyway, these are 
the things that are tricky to install.

Of course, someone has to prepare an installer, this amount of work 
doesn't magically disappear. But maybe it's a good idea to share common 
infrastructure, resources and knowledge with the Haskell Platform 
effort? Things that can be shared are:

* the guy with the hat on top (release manager) who prods people to stay 
in sync
* testing infrastructure (I have this romantic image where the Haskell 
Platforms hackers have access to a vast cloud of virtual machines to 
test their installation on different systems)
* shell scripts for automating the creation of installers. (I for one 
have no clue how to create an installer on MacOS X.)


So, the idea would be to have several installers: the Haskell Platform 
as a basis and then several "Pillars" on top, for instance the "GUI 
Pillar" that includes binaries for wxHaskell and GTK, or a "Web Pillar" 
that collects several web packages as soon as they become tricky to 
install with cabal ("yesod platform"). The latter should probably be a 
user install, not a global one.


Best regards,
Heinrich Apfelmus

--
http://apfelmus.nfshost.com

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[Antton T. <ant...@gm...>]

I haven't updated haskell platform to newest, but I would find it
strange if the old version stopped working. If you merely had to
rebuild wxhaskell, the issue might be that 0.9 and 0.13.2.1 target
version 2.9 by default. Wx-0.13.2.1 can be configured to use your 2.8
installation. I roughly outlined the process in previous post.
http://www.mail-archive.com/wxh...@li.../msg01139.html

As a side note, most of the mysterious cabal build errors I get (on
windows 7) are fixed by running
set LANG=C
in cmd before compiling (or setting it as permanent environment variable).

Installer would indeed be very nice, but it takes a lot of work to
create and maintain universal installer and it would currently benefit
only a handful of  people. I'm guessing the majority of wxhaskell
users are fairly savvy developers, so it would not seem worth the
trouble. That of course quickly becomes self fulfilling statement
since it will actively drive away people who have no interest in
fiddling with the nuances of the installation process. They may give
it a try, but fail and give up and you never hear from them.

I will devote some time on this if I end up using haskell on more
projects. Most people who wish to use wxhaskell are not likely to
participate in its development, but at the same time people are less
willing to develop a library with only few users. Haskell platform
itself is pretty much single click installation, and it is very easy
to get started with. Ideally that should be the case with every gui
toolkit as well.

Antton

On Thu, Jun 7, 2012 at 10:55 AM, David Virebayre
<dav...@gm...> wrote:
>
> I've never managed to get wxHaskell running without problems on windows,
> last time I tried there was some kind of encoding problem, and I gave up.
>
> That would be cool if there was an installer that would install wxHaskell
> with all dependences on top of a freshly installed haskell platform on
> windows.
>
> I would be eternally thankful if someone could do that.
>
> David.
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>

Re: [wxhaskell-users] Problems installing wxcore (space in path)

[Henk-Jan v. T. <hj...@ch...>]

On Wed, 06 Jun 2012 23:14:20 +0200, Henk-Jan van Tuyl <hj...@ch...>  
wrote:

> The following session seems to indicate that the setup of wxcore cannot
> handle a space in the pathname of the directory where packages are
> installed. I don't know how to change the location of this directory; any
> suggestions how to get wxcore installed? (System: Windows XP)
>
>> cabal install wx --global
> Resolving dependencies...
> [1 of 1] Compiling Main             (
> C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\Setup.hs,
> C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\dist\setup\Main.o
> )
> Linking
> C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\dist\setup\setup.exe
> ...
> Configuring wxcore-0.90.0.1...
> Generating class type definitions from .h files
> generating: src/haskell/Graphics/UI/WXCore/WxcClassTypes.hs
> reading class definitions:
> parsing: C:\Program/include/wxc.h
> wxdirect: C:\Program/include/wxc.h: openFile: does not exist (No such  
> file
> or directory)
> Generating class info definitions
> generating: src/haskell/Graphics/UI/WXCore/WxcClassInfo.hs
> reading class definitions:
> parsing: C:\Program/include/wxc.h
> wxdirect: C:\Program/include/wxc.h: openFile: does not exist (No such  
> file
> or directory)
> Generating class method definitions from .h files
> parsing: Files\Haskell\wxc-0.90.0.3\ghc-7.4.1\include/wxc.h
> wxdirect: Files\Haskell\wxc-0.90.0.3\ghc-7.4.1\include/wxc.h: openFile:
> does not exist (No such file or directory)

I have found a solution; I changed wxcore-0.90.0.1\setup.hs (added double  
quotes before and after filenames):
  - line 57 changed to:
     let wxcoreIncludeFile = "\"" ++ wxcDirectory </> "include/wxc.h\""
  - inserted after line 57:
     let wxcDirectory      = "\"" ++ wxcDirectory ++ "\""

This solution should be tested on other platforms.

Regards,
Henk-Jan van Tuyl


-- 
http://Van.Tuyl.eu/
http://members.chello.nl/hjgtuyl/tourdemonad.html
Haskell programming
--

Re: [wxhaskell-users] problems buiding wxHaskell on Windows

[David V. <dav...@gm...>]

I've never managed to get wxHaskell running without problems on windows,
last time I tried there was some kind of encoding problem, and I gave up.

That would be cool if there was an installer that would install wxHaskell
with all dependences on top of a freshly installed haskell platform on
windows.

I would be eternally thankful if someone could do that.

David.

[wxhaskell-users] Problems installing wxcore (space in path)

[Henk-Jan v. T. <hj...@ch...>]

L.S.,

The following session seems to indicate that the setup of wxcore cannot  
handle a space in the pathname of the directory where packages are  
installed. I don't know how to change the location of this directory; any  
suggestions how to get wxcore installed? (System: Windows XP)

> cabal install wx --global
Resolving dependencies...
[1 of 1] Compiling Main             (  
C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\Setup.hs,  
C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\dist\setup\Main.o  
)
Linking  
C:\DOCUME~1\User\LOCALS~1\Temp\wxcore-0.90.0.1-2708\wxcore-0.90.0.1\dist\setup\setup.exe  
...
Configuring wxcore-0.90.0.1...
Generating class type definitions from .h files
generating: src/haskell/Graphics/UI/WXCore/WxcClassTypes.hs
reading class definitions:
parsing: C:\Program/include/wxc.h
wxdirect: C:\Program/include/wxc.h: openFile: does not exist (No such file  
or directory)
Generating class info definitions
generating: src/haskell/Graphics/UI/WXCore/WxcClassInfo.hs
reading class definitions:
parsing: C:\Program/include/wxc.h
wxdirect: C:\Program/include/wxc.h: openFile: does not exist (No such file  
or directory)
Generating class method definitions from .h files
parsing: Files\Haskell\wxc-0.90.0.3\ghc-7.4.1\include/wxc.h
wxdirect: Files\Haskell\wxc-0.90.0.3\ghc-7.4.1\include/wxc.h: openFile:  
does not exist (No such file or directory)
setup.exe: Missing dependency on a foreign library:
* Missing C library: wxc
This problem can usually be solved by installing the system package that
provides this library (you may need the "-dev" version). If the library is
already installed but in a non-standard location then you can use the flags
--extra-include-dirs= and --extra-lib-dirs= to specify where it is.
cabal: Error: some packages failed to install:
wx-0.90.0.1 depends on wxcore-0.90.0.1 which failed to install.
wxcore-0.90.0.1 failed during the configure step. The exception was:
ExitFailure 1


Regards,
Henk-Jan van Tuyl


-- 
http://Van.Tuyl.eu/
http://members.chello.nl/hjgtuyl/tourdemonad.html
Haskell programming
--

[wxhaskell-users] problems buiding wxHaskell on Windows

[Gregory G. <gu...@mu...>]

After an upgrade to the new Haskell Platform, my existing wxHaskell programs are broken. They all seem to now require wxWidgets 2.9, for which I can't find any binary versions. wxPack has 2.8, and beyond that one has to get a compiler and build it locally from what I see.
There are tutorials on this from various sources, each a few pages long, with various advice on setup, changing configurations, etc. Install wxConfig, install minGW compilers, setup configurations, rebuild, etc.

Is there any source of a simple binary install? I'd hope for some simple apt-get or cabal like tool, Haskell library tools (on Windows?) seem less integrated than others that I'm familiar with.

I did follow the instructions at:
   http://www.haskell.org/haskellwiki/WxHaskell/Windows#wxWidgets_2.9_and_wxHaskell_0.90.x 

to install and compile wxWidgets locally, and still cannot get the wxHaskell components to install. I'm sure that all of this just requires some fairly simple details, but again after some time already, hope not to have to spend a lot more time on this, and wish it was more automated!

    >cabal install wxc
    ...
    Configuring wxc-0.90.0.3...
    Configuring wxc to build against wxWidgets 2.9

    setup.exe: Missing dependencies on foreign libraries:
    * Missing C libraries: wxmsw29ud_all, wxtiffd, wxjpegd, wxpngd, wxzlibd, wxregexud, wxexpatd, wxregexud
    This problem can usually be solved by installing the system packages that
    provide these libraries (you may need the "-dev" versions). If the libraries
    are already installed but in a non-standard location then you can use the
    flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
    cabal: Error: some packages failed to install:
    wx-0.90.0.1 depends on wxc-0.90.0.3 which failed to install.
    wxc-0.90.0.3 failed during the configure step. The exception was: ExitFailure 1
    wxcore-0.90.0.1 depends on wxc-0.90.0.3 which failed to install.

Someone on Haskell-beginners noted that it looks like I compiled wxWidgets, but did not install them - Could be, but the above instructions do not mention that.

I see in my cabal directory that it has files :
  Wx-0.12.1.6,
  Wxcore-0.12.1.7
  Wxdirect-0.12.1.4
  Wxdirect-0.90.0.1

I also notice that these instructions require a bunch of PATH fiddling that I never had to do before for wxWidgets /wxHaskell 2.8. 
Also that it asks to install a path pointer to the cabal directory to \wxc-%WXC_VERSION%\%GHC_VERSION% which file does not exist on my system.  ??