wxhaskell-users — General mailing list for wxhaskell users

[wxhaskell-users] Need Win-64 version of wx-config.exe

[Howard B. G. <how...@ya...>]

Hi,

I tried to install the wx-config.exe file at https://sourceforge.net/projects/wxhaskell/files/wx-config-win/ on Windows 7 Professional 64. It won't run because it is a 32-bit executable. If possible, please provide either a 64-bit version of wx-config.exe or the source code so I can recompile it for 64-bits.

It would be very helpful if you could submit your new version of wx-config for Windows to the original author of wx-config for Windows. I spent a lot of time recompiling the 2006 version and wondering why it wouldn't work with the latest wxHaskell.

Thank you for wxHaskell!

Howard B. Golden
Northridge, California USA

Re: [wxhaskell-users] wxHaskell - install problems..

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

On Wed, 20 Aug 2014 21:33:52 +0200, Gregory Guthrie <gu...@mu...>  
wrote:

> I did an upgrade to the current Haskell Platform (2014.2.0.0, = ghci  
> 7.8), and now wxHaskell seems to be broken.
>
> Environment seems to be OK:
>    WXC_VERSION = 0.90.0.3

It is better to install wxHaskell 0.91

>    GHC_Version = 7.8.3
>    WxWin = e:\plang\Libraries\wxWidgets-3.0.1
>    WxCfg = gcc_dll\mswu
> PATH set as per directions  
> (https://www.haskell.org/haskellwiki/WxHaskell/Windows).
> I do notice that page is in terms of Version 2.9.5, I am not sure how  
> that relates to the 3.0.1 version installed (as above).

The installation procedure is exactly the same, the page is updated in the  
meanwhile.

>
> I installed wxWidgets from: wxMSW-3.0.1-Setup
>
> I did not build from source, but instead used: wxMSW.exe;
> I also did a cabal install of (wx, wxcore), and all seemed to go well.
>
> But;
>     trying to run wxHello in GHCi fails - can't find uuid.dll

You have to install several DLLs as described in
   https://www.haskell.org/haskellwiki/WxHaskell/Windows#DLLs

GHCi cannot handle wxHaskell at the moment, see
   https://ghc.haskell.org/trac/ghc/ticket/7103

>
>    Trying to compile from GHC works, but execution fails: Cannot fine  
> procedure entry point wxBitmapToggleButton_Create in dynamic library  
> wxc.dll
>
>    Trying to run from Leksah, fails: cabal missing dependency GLFW -any

I will investigate these points.

Regards,
Henk-Jan van Tuyl


-- 
Folding@home
What if you could share your unused computer power to help find a cure? In  
just 5 minutes you can join the world's biggest networked computer and get  
us closer sooner. Watch the video.
http://folding.stanford.edu/


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

[wxhaskell-users] wxHaskell - install problems..

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

I did an upgrade to the current Haskell Platform (2014.2.0.0, = ghci 7.8), and now wxHaskell seems to be broken.

Environment seems to be OK:
   WXC_VERSION = 0.90.0.3
   GHC_Versin = 7.8.3
   WxWin = e:\plang\Libraries\wxWidgets-3.0.1
  WxCfg = gcc_dll\mswu
  
PATH set as per directions (https://www.haskell.org/haskellwiki/WxHaskell/Windows).
I do notice that page is in terms of Version 2.9.5, I am not sure how that relates to the 3.0.1 version installed (as above).

I installed wxWidgets from: wxMSW-3.0.1-Setup

I did not build from source, but instead used: wxMSW.exe; 
I also did a cabal install of (wx, wxcore), and all seemed to go well.

But;
    trying to run wxHello in GHCi fails - can't find uuid.dll

   Trying to compile from GHC works, but execution fails: Cannot fine procedure entry point wxBitmapToggleButton_Create in dynamic library wxc.dll

   Trying to run from Leksah, fails: cabal missing dependency GLFW -any

??
-------------------------------------------

[wxhaskell-users] Timer results in lockup

[Michael J. <mi...@pr...>]

I have an application using a timer with a 200ms interval. When I change the interval to 100ms, the application locks up.

I assumed the problem was a callback was made before the previous callback was complete. So I added an MVar to protect against executing IO in parallel.

With 200ms, the MVar code runs fine. But at 100mS it locks up. I tried to use putStrLn to prove that a try on MVar got a nothing and that the extra callback exited without any IO. However, I never saw any printing. But this could just be a problem of overlapping IO itself. What I was was callbacks that did not appear to overlap, followed by lockup. My assumption is the lockup happens before the callback can do a try on the MVar

Does anyone know:

- Will the timer callback if a previous callback is not complete?
- Is there any known lockup from overlapping callbacks?
- Is there a proper way to handling potential overlapping callbacks?

As far as I can tell, the only mechanism I have other than synchronization techniques, is to manipulate the interval from the callback.

- If the interval is lengthened and shortened, does the current time remain in tack?
- If the time is shortened, would it trigger an immediate callback if the time is less than the current timer?
- Or is the timer restarted with the interval changed?

I am using the latest version of wxHaskell. Just built it yesterday and wrote my first app. Using 3.0.1 on Ubuntu 14 TLS.

Mike

[wxhaskell-users] Timer results in lockup

[Michael J. <mi...@pr...>]

I have an application using a timer with a 200ms interval. When I change the interval to 100ms, the application locks up.

I assumed the problem was a callback was made before the previous callback was complete. So I added an MVar to protect against executing IO in parallel.

With 200ms, the MVar code runs fine. But at 100mS it locks up. I tried to use putStrLn to prove that a try on MVar got a nothing and that the extra callback exited without any IO. However, I never saw any printing. But this could just be a problem of overlapping IO itself. What I was was callbacks that did not appear to overlap, followed by lockup. My assumption is the lockup happens before the callback can do a try on the MVar

Does anyone know:

- Will the timer callback if a previous callback is not complete?
- Is there any known lockup from overlapping callbacks?
- Is there a proper way to handling potential overlapping callbacks?

As far as I can tell, the only mechanism I have other than synchronization techniques, is to manipulate the interval from the callback.

- If the interval is lengthened and shortened, does the current time remain in tack?
- If the time is shortened, would it trigger an immediate callback if the time is less than the current timer?
- Or is the timer restarted with the interval changed?

I am using the latest version of wxHaskell. Just built it yesterday and wrote my first app. Using 3.0.1 on Ubuntu 14 TLS.

Mike

[wxhaskell-users] ANNOUNCE: wxHaskell 0.91.0.0

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

L.S.,

I am happy to announce a new version of wxHaskell. This version binds to
both wxWidgets 2.9 and 3.0 [0]. As wxWidgets 3.0 is significantly better,
I advice everyone, who is already using wxHaskell, to upgrade to wxWidgets
3.0.1


What is it?
-----------
wxHaskell[1] is a portable and native GUI library for Haskell. The goal of
the project is to provide an industrial strength GUI library for Haskell,
but without the burden of developing (and maintaining) one ourselves.

wxHaskell is therefore built on top of wxWidgets – a comprehensive C++
library that is portable across all major GUI platforms; including GTK,
Windows, X11, and MacOS X. Furthermore, it is a mature library (in
development since 1992) that supports a wide range of widgets with the
native look-and-feel.


What's new?
-----------
  - Accept both wxWidgets 2.9 and 3.0, with a preference for 3.0
  - Added bindings for wxGraphicsContext::CreatePath
  - Use the same custom hook for `cabal copy` in wxc/Setup.hs
  - Many updates in definitions of constants and some 'deprecated'
    annotations
  - samples/wx/TestTaskBarIcon.hs now displays an icon in the taskbar
  - Parsec.hs can now handle lines starting with "//" properly
    (package wxdirect)
  - Fixed build issue that was caused by not having both
    the 2.9 and 3.0 versions of wxWidgets installed
  - Made samples/test/STCEvent.hs compilable
  - Solved warnings about deprecated methods and duplicate constant
    definition
  - Added -Wl to options for compiling wxc.dll
  - Adapted upper limit for packages process and array
  - Solved "deprecated" warning from GHC 7.8.2

Links
-----
See the homepage of wxHaskell for more information:
   https://www.haskell.org/haskellwiki/WxHaskell

The packages are:
  - wxc       https://hackage.haskell.org/package/wxc
  - wxdirect  https://hackage.haskell.org/package/wxdirect
  - wxcore    https://hackage.haskell.org/package/wxcore
  - wx        https://hackage.haskell.org/package/wx

Regards,
Henk-Jan van Tuyl


[0] https://www.wxwidgets.org
[1] https://www.haskell.org/haskellwiki/WxHaskell



--
Folding@home
What if you could share your unused computer power to help find a cure? In
just 5 minutes you can join the world's biggest networked computer and get
us closer sooner. Watch the video.
http://folding.stanford.edu/


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

[wxhaskell-users] ANNOUNCE: wxHaskell 0.90.1.0

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

L.S.,

I am happy to announce a new version of wxHaskell. This version binds to  
wxWidgets 2.9 [0].


What is it?
-----------
wxHaskell is a portable and native GUI library for Haskell. The goal of  
the project is to provide an industrial strength GUI library for Haskell,  
but without the burden of developing (and maintaining) one ourselves.

wxHaskell is therefore built on top of wxWidgets – a comprehensive C++  
library that is portable across all major GUI platforms; including GTK,  
Windows, X11, and MacOS X. Furthermore, it is a mature library (in  
development since 1992) that supports a wide range of widgets with the  
native look-and-feel.


What's new?
-----------
  - Added functionality: wxGrid: cell spans, cell renderers (numeric, auto  
string wrapping),
    wxScrolledWindow, wxSplitterWindow
  - Reanimated wxToggleButton, added wxBitmapToggleButton
  - Solved problem with spaces in pathnames (installation procedure,  
Windows)
  - Increased max version of dependencies
  - The external preprocessor (CPP) is now used
  - The presence of the wx-config executable is checked at installation time
  - The bitness of the wxWidgets dynamic libraries is compared to the  
bitness of the wxHaskell libraries
    to generate, at installation time; a warning is given when the bitness  
is incompatible
  - Documentation improvements
  - Bugs fixed


Links
-----
See the homepage of wxHaskell for more information:
   https://www.haskell.org/haskellwiki/WxHaskell

The packages are:
  - wxc       https://hackage.haskell.org/package/wxc
  - wxdirect  https://hackage.haskell.org/package/wxdirect
  - wxcore    https://hackage.haskell.org/package/wxcore
  - wx        https://hackage.haskell.org/package/wx

Regards,
Henk-Jan van Tuyl


[0] https://www.wxwidgets.org/


-- 
Folding@home
What if you could share your unused computer power to help find a cure? In  
just 5 minutes you can join the world's biggest networked computer and get  
us closer sooner. Watch the video.
http://folding.stanford.edu/


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

[wxhaskell-users] Drag and Drop : how to do this ?

[Luc T. <luc...@gm...>]

I am looking for wx Drag and Drop Example
Any available ?
So far:  
- I can see a on drag event ( no drop)
- mouse is just giving a left up on target
- I see some come where I am supposed to attache a drop target to on object , but I do not see how it is invoiced  
- also see data object attchaed to source and target

anyway, quite fuzzy for now...

--------------
Luc
be.linkedin.com/in/luctaesch/ (http://be.linkedin.com/in/luctaesch/)
Envoyé avec Sparrow (http://www.sparrowmailapp.com/?sig)

[wxhaskell-users] can we have a line that would be reactive ?

[Luc T. <luc...@gm...>]

can we have a line that would be reactive ? ( on select, on click, etc) ?
should I create a custom object , or anything native ?

context: 
I am drawing diagrams (schema) ( imagine ump or other mind mapping ), and I have used static text to have the text cickable. how can I do the same with lines ?
or Am I doomed to just detect the click point , and manage the mapping to the object myself ?)

Happy Easter
Luc

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

[Luc T. <luc...@gm...>]

>It might be a good idea if you could update the Haskell wiki with your config just so people know that it is possible in practice to get it working on Mountain Lion.

done.

I also changed this snippet . please check I am not mistake, Eric:

cabal-osx -> macosx-app

ghc --make HelloWorld.hs macosx-app HelloWorld ./HelloWorld.app/Contents/MacOS/HelloWorld

Thanks again for your , sharing, and dedication ;-)

Luc  

--------------
Luc
be.linkedin.com/in/luctaesch/ (http://be.linkedin.com/in/luctaesch/)
Envoyé avec Sparrow (http://www.sparrowmailapp.com/?sig)


Le mercredi 20 mars 2013 à 10:59, Eric Kow a écrit :

> Super! :-)
>  
> On 19 Mar 2013, at 20:32, Luc TAESCH wrote:
> > Now on the feedback side:  
> > - 1/ Macosx
> > ( once the line was compiled)
> > I thought it was failing because cabal-macosx was missing.
> > this step from [1] made me believe I was expecting an executable called cabal-macosx when in fact the exe generated was called macosx-app
> >  
>  
>  
> That's a good point. It's called macosx-app for historical reasons (we used to ship a shell script called macosx-app, but I'd welcome an thin wrapper called cabal-mocosx)
>  
> A good part of things “just working” is lining up with what a person would unconsciously expect, which is hard to do. But we have to keep chipping away at it.
>  
> > So many thnkas again , and this was the opportunity to realize the quick support I could get on wxHaskell !!
>  
> Now the bad news: we've not been very active lately, and you might have gotten a bit lucky (I was taking the day off from work yesterday), but hopefully this sort of thing can improve.
>  
> wxHaskell needs a lot more love.
> It's great to hear it working on a recent platform and MacOS X.
>  
> I've seen some Linux folks having some trouble lately, and am sorry not to be able to wheel my attention around to help them more.
>  
> It might be a good idea if you could update the Haskell wiki with your config just so people know that it is possible in practice to get it working on Mountain Lion.
>  
>  
>  
> --  
> Eric Kow <http://erickow.com>
>  
>  

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

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

Super! :-)

On 19 Mar 2013, at 20:32, Luc TAESCH wrote:
> Now on the feedback side: 
> - 1/ Macosx
> ( once the line was compiled)
> I thought it was failing because cabal-macosx was missing.
> this step from [1] made me believe I was expecting an executable called cabal-macosx when in fact the exe generated was called macosx-app

That's a good point.  It's called macosx-app for historical reasons (we used to ship a shell script called macosx-app, but I'd welcome an thin wrapper called cabal-mocosx)

A good part of things “just working” is lining up with what a person would unconsciously expect, which is hard to do.  But we have to keep chipping away at it.

> So many thnkas again , and this was the opportunity to realize the quick support I could get on wxHaskell !!

Now the bad news: we've not been very active lately, and you might have gotten a bit lucky (I was taking the day off from work yesterday), but hopefully this sort of thing can improve.

wxHaskell needs a lot more love.
It's great to hear it working on a recent platform and MacOS X.

I've seen some Linux folks having some trouble lately, and am sorry not to be able to wheel my attention around to help them more.

It might be a good idea if you could update the Haskell wiki with your config just so people know that it is possible in practice to get it working on Mountain Lion.



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

Re: [wxhaskell-users] cabal-macosx

[Luc T. <luc...@gm...>]

my mistake , I run the build , not the install !!  

once done, it went fine , many thanks again for your time and availability !!
( and quick response)

Luc
-------
mbp2-de-luc:wxHello luc$ cabal clean
cleaning...

mbp2-de-luc:wxHello luc$ cabal configure
Resolving dependencies...
[1 of 1] Compiling Main             ( Setup.hs, dist/setup/Main.o )
Linking ./dist/setup/setup ...
Configuring wxHello-0.1.0...
mbp2-de-luc:wxHello luc$ cabal build     
Building wxHello-0.1.0...
Preprocessing executable 'WxHello' for wxHello-0.1.0...
[1 of 1] Compiling Main             ( src/Main.hs, dist/build/WxHello/WxHello-tmp/Main.o )

src/Main.hs:10:10:
    Warning: A do-notation statement discarded a result of type StaticText
                                                                  ().
             Suppress this warning by saying "_ <- staticText
                                                     f
                                                     [(Graphics.UI.WX.Attributes.:=)
                                                        text "How you doing?"]",
             or by using the flag -fno-warn-unused-do-bind
Linking dist/build/WxHello/WxHello ...
Creating application bundle directory dist/build/WxHello.app
Copying executable WxHello into place
Copying resources/WxHello.icns to app's icon
Running Rez, etc.
mbp2-de-luc:wxHello luc$  




--------------
Luc
be.linkedin.com/in/luctaesch/ (http://be.linkedin.com/in/luctaesch/)
Envoyé avec Sparrow (http://www.sparrowmailapp.com/?sig)


Le mardi 19 mars 2013 à 22:04, Eric Kow a écrit :

> Distribution.MacOSX comes from the cabal-macosx package.
> It's a funny situation where the Setup.hs (for wxHaselo) depends on cabal-macosx
>  
> On 19 Mar 2013, at 21:01, luc taesch wrote:
>  
> > when trying to test the examples
> > i got the following error ( the stanad alone program does work)
> >  
> >  
> > how ever , I could see the Distribution.Macosx directory full of .o and .hi
> > shoud it build and regiser a lib some where ?
> >  
> > ( source is github )
> >  
> > mbp2-de-luc:~ luc$ cd /Volumes/Macintosh\  
> > HD/Users/luc/Documents/haskell/cabal-macosx/examples/wxHello
> > mbp2-de-luc:wxHello luc$ cabal configure
> > Resolving dependencies...
> >  
> > Setup.hs:3:8:
> > Could not find module `Distribution.MacOSX'
> > Perhaps you meant
> > Distribution.Make (from Cabal-1.16.0.3)
> > Distribution.Make (needs flag -package Cabal-1.14.0)
> > Distribution.Package (needs flag -package Cabal-1.14.0)
> > Use -v to see a list of the files searched for.
> >  
> >  
> >  
> > ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_d2d_mar
> > _______________________________________________
> > wxhaskell-users mailing list
> > wxh...@li... (mailto:wxh...@li...)
> > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
> >  
>  
>  
> --  
> Eric Kow <http://erickow.com>
>  
>  

Re: [wxhaskell-users] cabal-macosx

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

Distribution.MacOSX comes from the cabal-macosx package.
It's a funny situation where the Setup.hs (for wxHaselo) depends on cabal-macosx

On 19 Mar 2013, at 21:01, luc taesch wrote:

> when trying to test the examples
> i got the following error ( the stanad alone program does work)
> 
> 
> how ever , I could see the Distribution.Macosx directory full of .o and .hi
> shoud it build and regiser a lib some where ?
> 
> ( source is github )
> 
> mbp2-de-luc:~ luc$ cd /Volumes/Macintosh\ 
> HD/Users/luc/Documents/haskell/cabal-macosx/examples/wxHello
> mbp2-de-luc:wxHello luc$ cabal configure
> Resolving dependencies...
> 
> Setup.hs:3:8:
>    Could not find module `Distribution.MacOSX'
>    Perhaps you meant
>      Distribution.Make (from Cabal-1.16.0.3)
>      Distribution.Make (needs flag -package Cabal-1.14.0)
>      Distribution.Package (needs flag -package Cabal-1.14.0)
>    Use -v to see a list of the files searched for.
> 
> 
> 
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

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

[wxhaskell-users] cabal-macosx

[luc t. < <luc...@gm...>]

when trying to test the examples
i got the following error ( the stanad alone program does work)


how ever , I could see the Distribution.Macosx directory full of .o and .hi
shoud it build and regiser a lib some where ?

( source is github )

mbp2-de-luc:~ luc$ cd /Volumes/Macintosh\ 
HD/Users/luc/Documents/haskell/cabal-macosx/examples/wxHello
mbp2-de-luc:wxHello luc$ cabal configure
Resolving dependencies...

Setup.hs:3:8:
    Could not find module `Distribution.MacOSX'
    Perhaps you meant
      Distribution.Make (from Cabal-1.16.0.3)
      Distribution.Make (needs flag -package Cabal-1.14.0)
      Distribution.Package (needs flag -package Cabal-1.14.0)
    Use -v to see a list of the files searched for.

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

[Luc T. <luc...@gm...>]

ok, all sorted! Thanks !!
- in short :  I reinstalled HP in 64,and it all went fine.
-  could check the three test of debug_wx, and pass a few example from wx ( controls.hs and so on)

THIS IS THE FIRST GUI LIB I CAN HAVE WORKING  ON MAC OS FOR YEARS ! MANY THANKS !


Now on the feedback side:  
- 1/ Macosx
( once the line was compiled)
I thought it was failing because cabal-macosx was missing.
this step from [1] made me believe I was expecting an executable called cabal-macosx when in fact the exe generated was called macosx-app

Compile and run a sample wxcore application (https://raw.github.com/jodonoghue/wxHaskell/master/samples/wxcore/HelloWorld.hs):  
ghc --make HelloWorld.hs cabal-macosx HelloWorld ./HelloWorld.app/Contents/MacOS/HelloWorld


but it is not an error , as this cabal extract shows :

Executable macosx-app
  Main-is:         macosx-app.hs


and Macosx  des the job of creating an app
So I think this is just the doc that may be out of date

[1](http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X)

2/ the HP did not erased the 32 bit version not did cleaned my .cabal file ( diverse exe still living in it)
I did it by hand to be sure


So many thnkas again , and this was the opportunity to realize the quick support I could get on wxHaskell !!

Luc



Le mardi 19 mars 2013 à 17:21, Eric Kow a écrit :

> The HP installer comes with a removal tool you can use, I think
> I don't think I have a really good answer to your other questions, though.
>  
>  
> On 19 Mar 2013, at 16:18, Luc TAESCH wrote:
>  
> > How can I make sure all is cleaned before I install a 64 platform ? i.e. no 32 residue ?
> > any way to clean , automated ?
> >  
>  
>  
> --  
> Eric Kow <http://erickow.com>
>  
>  

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

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

The HP installer comes with a removal tool you can use, I think
I don't think I have a really good answer to your other questions, though.


On 19 Mar 2013, at 16:18, Luc TAESCH wrote:

> How can I make sure all is cleaned before I install a 64 platform ? i.e. no 32 residue ?
> any way to clean , automated ?
> 

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

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

[Luc T. <luc...@gm...>]

How can I make sure all is cleaned before I install a 64 platform ? i.e. no 32 residue ?
any way to clean , automated ?

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

[Luc T. <luc...@gm...>]

Many thanks for your help again:

/usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib: Mach-O 64-bit dynamically linked shared library x86_64

mbp2-de-luc:~ luc$  cat /usr/bin/ghc
#!/bin/sh
exedir="/Library/Frameworks/GHC.framework/Versions/7.4.2-i386/usr/lib/ghc-7.4.2"
exeprog="ghc-stage2"
executablename="$exedir/$exeprog"
datadir="/Library/Frameworks/GHC.framework/Versions/7.4.2-i386/usr/share"
bindir="/Library/Frameworks/GHC.framework/Versions/7.4.2-i386/usr/bin"
topdir="/Library/Frameworks/GHC.framework/Versions/7.4.2-i386/usr/lib/ghc-7.4.2"
executablename="$exedir/ghc"
exec "$executablename" -B"$topdir" ${1+"$@"}
mbp2-de-luc:~ luc$  


how may I know ( from this script) of this is 32 or 64 ?

in the meantime , I found old wx lib fro 2010 in /usr/local, which I cleaned everything wx, ,  reinstalled the latest build ( 64 as shown before)
I check any pkg , de registeretred any wx package and reinstalled after th epeevious step

I thought it would do it, but no, the wxcore test is still funny:

does the message means it is expecting 32 : which is not the architecture being linked (i386) ?

what are the consequence of switching to GHC 64 ?


mbp2-de-luc:wxcore luc$ ghc --make HelloWorld
[1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
Linking HelloWorld ...
ld: warning: ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_webview-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_webview-2.9.dylibignoring file /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib

ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_stc-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_stc-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_richtext-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_richtext-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_aui-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_aui-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_gl-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_gl-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_qa-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_qa-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_html-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_html-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_adv-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_adv-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_core-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_core-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_baseu_xml-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu_xml-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_baseu_net-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu_net-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_baseu-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu-2.9.dylib
mbp2-de-luc:wxcore luc$  



--------------
Luc
be.linkedin.com/in/luctaesch/ (http://be.linkedin.com/in/luctaesch/)
Envoyé avec Sparrow (http://www.sparrowmailapp.com/?sig)


Le mardi 19 mars 2013 à 16:56, Eric Kow a écrit :

> What does `file /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib` report?
> And what about `cat /usr/bin/ghc`? (It should be a shell script)
>  
> Just trying to find out if you have a 64 bit wxWidgets with 32 bit GHC which may be the case
> If that's so, you might have better luck with the 64 bit GHC
>  
>  
> On 19 Mar 2013, at 15:19, Luc TAESCH wrote:
>  
> > > - using debug-wx to see what stage things go wrong at? https://github.com/kowey/debug-wx
> > (it's a collection of hello worlds for different layers)
> >  
> > Very helpful , thanks. Steps1 ok. Step 2 break
> >  
> > mbp2-de-luc:debug-wx luc$ wx-config
> >  
> > wx-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--release] [--version-full]
> > [--list] [--selected-config] [--host=HOST] [--toolkit=TOOLKIT]
> > [--universal[=yes|no]] [--unicode[=yes|no]] [--static[=yes|no]]
> > [--debug[=yes|no]] [--version[=VERSION]] [--basename] [--cc] [--cxx]
> > [--cppflags [base]] [--cxxflags [base]] [--cflags]
> > [--rescomp] [--linkdeps] [--ld] [--utility=UTIL]
> > [--libs [LIBS...]] [--optional-libs [LIBS...]]
> >  
> > wx-config returns information about the wxWidgets libraries available on
> > your system. It may be used to retrieve the information required to build
> > applications using these libraries using --cppflags, --cxxflags, --cflags,
> > and --libs options. And you may query the properties of this configuration
> > using --query-{host,toolkit,widgetset,chartype,debugtype,version,linkage}.
> >  
> > NOTE: Usage of --debug and --query-debugtype are only relevant if you
> > have any versions prior to 2.9 installed and use the --version option to
> > select an earlier version.
> >  
> > If multiple builds of wxWidgets are available, you can use the options
> > --prefix, --host, --toolkit, --unicode, --static, --universal or --version
> > to select from them. The --selected-config option shows the name of the
> > current configuration and --list shows available alternatives which match
> > specified criteria. The --utility option returns the correct version of
> > UTIL to use with the selected build. The --linkdeps option returns only
> > static libraries for your makefile link rule dependencies.
> >  
> > The LIBS arguments (comma or space separated) may be used to specify the
> > wxWidgets libraries that you wish to use. The "std" label may be used to
> > import all libraries that would be used by default if none were specified
> > explicitly, e.g. wx-config --libs core,base. The "all" label may be used
> > to import all libraries that have been compiled which are shown in the
> > list below. The --optional-libs parameter should be followed by a list
> > of libs that should be linked to, but only if they are available.
> >  
> > Available libraries in this build are:
> > xrc webview stc richtext ribbon propgrid aui gl html qa adv core xml net base
> >  
> > mbp2-de-luc:debug-wx luc$ cd wxWidgets
> > mbp2-de-luc:wxWidgets luc$ g++ minimal.cpp `wx-config --libs --cflags` -o minimal
> > mbp2-de-luc:wxWidgets luc$ ./minimal  
> >  
> > Step 2:
> >  
> > mbp2-de-luc:wxWidgets luc$ cd ..
> > mbp2-de-luc:debug-wx luc$ cd wxcore
> > mbp2-de-luc:wxcore luc$ ghc --make HelloWorld
> > [1 of 1] Compiling Main ( HelloWorld.hs, HelloWorld.o )
> > Linking HelloWorld ...
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_webview-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_webview-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_stc-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_stc-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_richtext-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_richtext-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_aui-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_aui-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_gl-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_gl-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_html-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_html-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_qa-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_qa-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_adv-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_adv-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_core-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_core-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_baseu_xml-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu_xml-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_baseu_net-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu_net-2.9.dylib
> > ld: warning: ignoring file /usr/local/lib/libwx_baseu-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu-2.9.dylib
> > mbp2-de-luc:wxcore luc$ ./HelloWorld  
> > dyld: Symbol not found: __ZN10wxDateTime13TIME_T_FACTORE
> > Referenced from: /Users/luc/.cabal/lib/wxc-0.90.0.4/ghc-7.4.2/libwxc.dylib
> > Expected in: flat namespace
> > in /Users/luc/.cabal/lib/wxc-0.90.0.4/ghc-7.4.2/libwxc.dylib
> > Trace/BPT trap: 5
> > mbp2-de-luc:wxcore luc$  
> >  
> > --------------
> > Luc
> > be.linkedin.com/in/luctaesch/ (http://be.linkedin.com/in/luctaesch/)
> > Envoyé avec Sparrow
> >  
> > Le mardi 19 mars 2013 à 15:38, Eric Kow a écrit :
> >  
> > > Do any of the following help?
> > >  
> > > - making sure you have a 64bit wxWidgets
> > > - using debug-wx to see what stage things go wrong at? https://github.com/kowey/debug-wx
> > > (it's a collection of hello worlds for different layers)
> > > - using my cabal-macosx branch? https://github.com/kowey/cabal-macosx
> > >  
> > > I might have forgotten to do a release, in which case sorry.
> > >  
> > > I'm on Lion, using ghc 7.4.1, wxWidgets from the Homebrew installer
> > >  
> > >  
> > > On 19 Mar 2013, at 00:01, luc taesch wrote:
> > >  
> > > > Are there any setup to do after install , (the equivalent of LD_CONFIG ?)
> > > >  
> > > > what i did , following [0 ]
> > > >  
> > > > 1/ install wxwigets went fine
> > > >  
> > > > 2/ but I cannot get a helllo world example running .
> > > > the cabal-macosx does not seems to be seen ( what
> > > > is expected in fact ?). any setup ?
> > > >  
> > > >  
> > > > 3/ trying and run the sample by hand raise an Error
> > > >  
> > > > Anyway this is much farther I ever been on a haskell gui install on the mac.
> > > > but not good enough so far.
> > > > I would love trying reactive banana.
> > > >  
> > > > ar there any positive experience of installing wx on 10.8
> > > > ( according to [0], yes) ?
> > > > any tricks to know ?
> > > >  
> > > >  
> > > > details here : http://hpaste.org/84285 due to size limitations.
> > > >  
> > > > [0]: http://www.haskell.org/haskellwiki/WxHaskell/Mac ( manual compile)
> > > >  
> > > >  
> > > > ------------------------------------------------------------------------------
> > > > Everyone hates slow websites. So do we.
> > > > Make your web apps faster with AppDynamics
> > > > Download AppDynamics Lite for free today:
> > > > http://p.sf.net/sfu/appdyn_d2d_mar
> > > > _______________________________________________
> > > > wxhaskell-users mailing list
> > > > wxh...@li... (mailto:wxh...@li...)
> > > > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
> > > >  
> > >  
> > >  
> > > --
> > > Eric Kow <http://erickow.com>
> > >  
> >  
> >  
>  
>  
> --  
> Eric Kow <http://erickow.com>
>  
>  

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

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

What does `file /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib` report?
And what about `cat /usr/bin/ghc`? (It should be a shell script)

Just trying to find out if you have a 64 bit wxWidgets with 32 bit GHC which may be the case
If that's so, you might have better luck with the 64 bit GHC


On 19 Mar 2013, at 15:19, Luc TAESCH wrote:

> >- using debug-wx to see what stage things go wrong at? https://github.com/kowey/debug-wx
> (it's a collection of hello worlds for different layers)
> 
> Very helpful , thanks. Steps1 ok. Step 2 break
> 
> mbp2-de-luc:debug-wx luc$ wx-config
> 
>  wx-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--release] [--version-full]
>            [--list] [--selected-config] [--host=HOST] [--toolkit=TOOLKIT]
>            [--universal[=yes|no]] [--unicode[=yes|no]] [--static[=yes|no]]
>            [--debug[=yes|no]] [--version[=VERSION]] [--basename] [--cc] [--cxx]
>            [--cppflags [base]] [--cxxflags [base]] [--cflags]
>            [--rescomp] [--linkdeps] [--ld] [--utility=UTIL]
>            [--libs [LIBS...]] [--optional-libs [LIBS...]]
> 
>     wx-config returns information about the wxWidgets libraries available on
>   your system.  It may be used to retrieve the information required to build
>   applications using these libraries using --cppflags, --cxxflags, --cflags,
>   and --libs options. And you may query the properties of this configuration
>   using --query-{host,toolkit,widgetset,chartype,debugtype,version,linkage}.
> 
>     NOTE:    Usage of --debug and --query-debugtype are only relevant if you
>   have any  versions prior to 2.9 installed  and use the --version option to
>   select an earlier version.
> 
>     If multiple builds of wxWidgets  are available,  you can use the options
>   --prefix, --host, --toolkit, --unicode, --static, --universal or --version
>   to select from them.  The  --selected-config  option shows the name of the
>   current configuration and --list  shows available alternatives which match
>   specified criteria.  The  --utility  option returns the correct version of
>   UTIL to use with the selected build.  The  --linkdeps  option returns only
>   static libraries for your makefile link rule dependencies.
> 
>     The LIBS arguments (comma or space separated) may be used to specify the
>   wxWidgets libraries that  you wish to use. The "std" label may be used  to
>   import all libraries that would be used by default if none were  specified
>   explicitly, e.g. wx-config --libs core,base. The "all" label may  be  used
>   to  import  all libraries that have been compiled which are shown  in  the
>   list  below.  The  --optional-libs parameter should be followed by  a list
>   of  libs that should be linked to, but only if they are available.
> 
>   Available libraries in this build are:
>   xrc webview stc richtext ribbon propgrid aui gl html qa adv core xml net base
> 
> mbp2-de-luc:debug-wx luc$ cd wxWidgets
> mbp2-de-luc:wxWidgets luc$ g++ minimal.cpp `wx-config --libs --cflags` -o minimal
> mbp2-de-luc:wxWidgets luc$ ./minimal 
> 
> Step 2:
> 
> mbp2-de-luc:wxWidgets luc$ cd ..
> mbp2-de-luc:debug-wx luc$ cd wxcore
> mbp2-de-luc:wxcore luc$ ghc --make HelloWorld
> [1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
> Linking HelloWorld ...
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_webview-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_webview-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_stc-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_stc-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_richtext-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_richtext-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_aui-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_aui-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_gl-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_gl-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_html-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_html-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_qa-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_qa-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_adv-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_adv-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_core-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_core-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_baseu_xml-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu_xml-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_baseu_net-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu_net-2.9.dylib
> ld: warning: ignoring file /usr/local/lib/libwx_baseu-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu-2.9.dylib
> mbp2-de-luc:wxcore luc$ ./HelloWorld 
> dyld: Symbol not found: __ZN10wxDateTime13TIME_T_FACTORE
>   Referenced from: /Users/luc/.cabal/lib/wxc-0.90.0.4/ghc-7.4.2/libwxc.dylib
>   Expected in: flat namespace
>  in /Users/luc/.cabal/lib/wxc-0.90.0.4/ghc-7.4.2/libwxc.dylib
> Trace/BPT trap: 5
> mbp2-de-luc:wxcore luc$ 
> 
> --------------
> Luc
> be.linkedin.com/in/luctaesch/
> Envoyé avec Sparrow
> 
> Le mardi 19 mars 2013 à 15:38, Eric Kow a écrit :
> 
>> Do any of the following help?
>> 
>> - making sure you have a 64bit wxWidgets
>> - using debug-wx to see what stage things go wrong at? https://github.com/kowey/debug-wx
>> (it's a collection of hello worlds for different layers)
>> - using my cabal-macosx branch? https://github.com/kowey/cabal-macosx
>> 
>> I might have forgotten to do a release, in which case sorry.
>> 
>> I'm on Lion, using ghc 7.4.1, wxWidgets from the Homebrew installer
>> 
>> 
>> On 19 Mar 2013, at 00:01, luc taesch wrote:
>> 
>>> Are there any setup to do after install , (the equivalent of LD_CONFIG ?)
>>> 
>>> what i did , following [0 ]
>>> 
>>> 1/ install wxwigets went fine
>>> 
>>> 2/ but I cannot get a helllo world example running .
>>> the cabal-macosx does not seems to be seen ( what
>>> is expected in fact ?). any setup ?
>>> 
>>> 
>>> 3/ trying and run the sample by hand raise an Error
>>> 
>>> Anyway this is much farther I ever been on a haskell gui install on the mac.
>>> but not good enough so far.
>>> I would love trying reactive banana.
>>> 
>>> ar there any positive experience of installing wx on 10.8
>>> ( according to [0], yes) ?
>>> any tricks to know ?
>>> 
>>> 
>>> details here : http://hpaste.org/84285 due to size limitations.
>>> 
>>> [0]: http://www.haskell.org/haskellwiki/WxHaskell/Mac ( manual compile)
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Everyone hates slow websites. So do we.
>>> Make your web apps faster with AppDynamics
>>> Download AppDynamics Lite for free today:
>>> http://p.sf.net/sfu/appdyn_d2d_mar
>>> _______________________________________________
>>> wxhaskell-users mailing list
>>> wxh...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>> 
>> --
>> Eric Kow <http://erickow.com>
> 

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

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

[Luc T. <luc...@gm...>]

>- using debug-wx to see what stage things go wrong at? https://github.com/kowey/debug-wx
(it's a collection of hello worlds for different layers)

Very helpful , thanks. Steps1 ok. Step 2 break

mbp2-de-luc:debug-wx luc$ wx-config

 wx-config [--prefix[=DIR]] [--exec-prefix[=DIR]] [--release] [--version-full]
           [--list] [--selected-config] [--host=HOST] [--toolkit=TOOLKIT]
           [--universal[=yes|no]] [--unicode[=yes|no]] [--static[=yes|no]]
           [--debug[=yes|no]] [--version[=VERSION]] [--basename] [--cc] [--cxx]
           [--cppflags [base]] [--cxxflags [base]] [--cflags]
           [--rescomp] [--linkdeps] [--ld] [--utility=UTIL]
           [--libs [LIBS...]] [--optional-libs [LIBS...]]

    wx-config returns information about the wxWidgets libraries available on
  your system.  It may be used to retrieve the information required to build
  applications using these libraries using --cppflags, --cxxflags, --cflags,
  and --libs options. And you may query the properties of this configuration
  using --query-{host,toolkit,widgetset,chartype,debugtype,version,linkage}.

    NOTE:    Usage of --debug and --query-debugtype are only relevant if you
  have any  versions prior to 2.9 installed  and use the --version option to
  select an earlier version.

    If multiple builds of wxWidgets  are available,  you can use the options
  --prefix, --host, --toolkit, --unicode, --static, --universal or --version
  to select from them.  The  --selected-config  option shows the name of the
  current configuration and --list  shows available alternatives which match
  specified criteria.  The  --utility  option returns the correct version of
  UTIL to use with the selected build.  The  --linkdeps  option returns only
  static libraries for your makefile link rule dependencies.

    The LIBS arguments (comma or space separated) may be used to specify the
  wxWidgets libraries that  you wish to use. The "std" label may be used  to
  import all libraries that would be used by default if none were  specified
  explicitly, e.g. wx-config --libs core,base. The "all" label may  be  used
  to  import  all libraries that have been compiled which are shown  in  the
  list  below.  The  --optional-libs parameter should be followed by  a list
  of  libs that should be linked to, but only if they are available.

  Available libraries in this build are:
  xrc webview stc richtext ribbon propgrid aui gl html qa adv core xml net base

mbp2-de-luc:debug-wx luc$ cd wxWidgets
mbp2-de-luc:wxWidgets luc$ g++ minimal.cpp `wx-config --libs --cflags` -o minimal
mbp2-de-luc:wxWidgets luc$ ./minimal  

Step 2:

mbp2-de-luc:wxWidgets luc$ cd ..
mbp2-de-luc:debug-wx luc$ cd wxcore
mbp2-de-luc:wxcore luc$ ghc --make HelloWorld
[1 of 1] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
Linking HelloWorld ...
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_xrc-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_webview-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_webview-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_stc-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_stc-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_richtext-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_richtext-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_aui-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_aui-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_gl-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_gl-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_html-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_html-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_qa-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_qa-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_adv-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_adv-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_osx_cocoau_core-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_osx_cocoau_core-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_baseu_xml-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu_xml-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_baseu_net-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu_net-2.9.dylib
ld: warning: ignoring file /usr/local/lib/libwx_baseu-2.9.dylib, file was built for unsupported file format ( 0xcf 0xfa 0xed 0xfe 0x 7 0x 0 0x 0 0x 1 0x 3 0x 0 0x 0 0x 0 0x 6 0x 0 0x 0 0x 0 ) which is not the architecture being linked (i386): /usr/local/lib/libwx_baseu-2.9.dylib
mbp2-de-luc:wxcore luc$ ./HelloWorld  
dyld: Symbol not found: __ZN10wxDateTime13TIME_T_FACTORE
  Referenced from: /Users/luc/.cabal/lib/wxc-0.90.0.4/ghc-7.4.2/libwxc.dylib
  Expected in: flat namespace
 in /Users/luc/.cabal/lib/wxc-0.90.0.4/ghc-7.4.2/libwxc.dylib
Trace/BPT trap: 5
mbp2-de-luc:wxcore luc$  


--------------
Luc
be.linkedin.com/in/luctaesch/ (http://be.linkedin.com/in/luctaesch/)
Envoyé avec Sparrow (http://www.sparrowmailapp.com/?sig)


Le mardi 19 mars 2013 à 15:38, Eric Kow a écrit :

> Do any of the following help?
>  
> - making sure you have a 64bit wxWidgets
> - using debug-wx to see what stage things go wrong at? https://github.com/kowey/debug-wx
> (it's a collection of hello worlds for different layers)
> - using my cabal-macosx branch? https://github.com/kowey/cabal-macosx
>  
> I might have forgotten to do a release, in which case sorry.
>  
> I'm on Lion, using ghc 7.4.1, wxWidgets from the Homebrew installer
>  
>  
> On 19 Mar 2013, at 00:01, luc taesch wrote:
>  
> > Are there any setup to do after install , (the equivalent of LD_CONFIG ?)
> >  
> > what i did , following [0 ]
> >  
> > 1/ install wxwigets went fine
> >  
> > 2/ but I cannot get a helllo world example running .  
> > the cabal-macosx does not seems to be seen ( what  
> > is expected in fact ?). any setup ?
> >  
> >  
> > 3/ trying and run the sample by hand raise an Error
> >  
> > Anyway this is much farther I ever been on a haskell gui install on the mac.
> > but not good enough so far.
> > I would love trying reactive banana.
> >  
> > ar there any positive experience of installing wx on 10.8  
> > ( according to [0], yes) ?  
> > any tricks to know ?
> >  
> >  
> > details here : http://hpaste.org/84285 due to size limitations.
> >  
> > [0]: http://www.haskell.org/haskellwiki/WxHaskell/Mac ( manual compile)
> >  
> >  
> > ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_d2d_mar
> > _______________________________________________
> > wxhaskell-users mailing list
> > wxh...@li... (mailto:wxh...@li...)
> > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
> >  
>  
>  
> --  
> Eric Kow <http://erickow.com>
>  
>  

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

[Luc T. <luc...@gm...>]

very kind for the reply, thanks
>- making sure you have a 64bit wxWidgets
How can I do this ?


--------------
Luc
be.linkedin.com/in/luctaesch/ (http://be.linkedin.com/in/luctaesch/)
Envoyé avec Sparrow (http://www.sparrowmailapp.com/?sig)


Le mardi 19 mars 2013 à 15:38, Eric Kow a écrit :

> Do any of the following help?
>  
> - making sure you have a 64bit wxWidgets
> - using debug-wx to see what stage things go wrong at? https://github.com/kowey/debug-wx
> (it's a collection of hello worlds for different layers)
> - using my cabal-macosx branch? https://github.com/kowey/cabal-macosx
>  
> I might have forgotten to do a release, in which case sorry.
>  
> I'm on Lion, using ghc 7.4.1, wxWidgets from the Homebrew installer
>  
>  
> On 19 Mar 2013, at 00:01, luc taesch wrote:
>  
> > Are there any setup to do after install , (the equivalent of LD_CONFIG ?)
> >  
> > what i did , following [0 ]
> >  
> > 1/ install wxwigets went fine
> >  
> > 2/ but I cannot get a helllo world example running .  
> > the cabal-macosx does not seems to be seen ( what  
> > is expected in fact ?). any setup ?
> >  
> >  
> > 3/ trying and run the sample by hand raise an Error
> >  
> > Anyway this is much farther I ever been on a haskell gui install on the mac.
> > but not good enough so far.
> > I would love trying reactive banana.
> >  
> > ar there any positive experience of installing wx on 10.8  
> > ( according to [0], yes) ?  
> > any tricks to know ?
> >  
> >  
> > details here : http://hpaste.org/84285 due to size limitations.
> >  
> > [0]: http://www.haskell.org/haskellwiki/WxHaskell/Mac ( manual compile)
> >  
> >  
> > ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> > http://p.sf.net/sfu/appdyn_d2d_mar
> > _______________________________________________
> > wxhaskell-users mailing list
> > wxh...@li... (mailto:wxh...@li...)
> > https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
> >  
>  
>  
> --  
> Eric Kow <http://erickow.com>
>  
>  

Re: [wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

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

Do any of the following help?

- making sure you have a 64bit wxWidgets
- using debug-wx to see what stage things go wrong at? https://github.com/kowey/debug-wx
  (it's a collection of hello worlds for different layers)
- using my cabal-macosx branch? https://github.com/kowey/cabal-macosx

I might have forgotten to do a release, in which case sorry.

I'm on Lion, using ghc 7.4.1, wxWidgets from the Homebrew installer


On 19 Mar 2013, at 00:01, luc taesch wrote:

> Are there any setup to do after install ,  (the equivalent of LD_CONFIG ?)
> 
> what i did , following [0 ]
> 
> 1/ install wxwigets went fine
> 
> 2/ but I cannot get a helllo  world example running . 
> the cabal-macosx does not seems to be seen ( what 
> is expected in fact ?). any setup ?
> 
> 
> 3/ trying and run the sample by hand raise an Error
> 
> Anyway this is much farther I ever been on a haskell gui install on the mac.
> but not good enough so far.
> I would love trying reactive banana.
> 
> ar there any positive experience of installing wx on 10.8 
> ( according to  [0], yes) ? 
> any tricks to know ?
> 
> 
> details here : http://hpaste.org/84285 due to size limitations.
> 
> [0]: http://www.haskell.org/haskellwiki/WxHaskell/Mac ( manual compile)
> 
> 
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_mar
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

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

[wxhaskell-users] first attempt on osx 10.8 - ghc7.4.2 -wx 2.9.4

[luc t. <luc...@gm...>]

Are there any setup to do after install ,  (the equivalent of LD_CONFIG ?)

what i did , following [0 ]

1/ install wxwigets went fine

2/ but I cannot get a helllo  world example running . 
the cabal-macosx does not seems to be seen ( what 
is expected in fact ?). any setup ?


3/ trying and run the sample by hand raise an Error

Anyway this is much farther I ever been on a haskell gui install on the mac.
but not good enough so far.
I would love trying reactive banana.

ar there any positive experience of installing wx on 10.8 
( according to  [0], yes) ? 
any tricks to know ?


details here : http://hpaste.org/84285 due to size limitations.

 [0]: http://www.haskell.org/haskellwiki/WxHaskell/Mac ( manual compile)

Re: [wxhaskell-users] Question about how to install WxHakell on Ubuntu and Win7

[Maciek M. <ma...@mm...>]

Regarding the Ubuntu setup, wxHaskell 0.90 requires wxWidgets 2.9, which
are not packaged for Ubuntu as far as I know. You can try `cabal install
wx-0.13.2.3` for a version of wxHaskell compatible with wxWidgets 2.8, or
build wxWidgets 2.9 from source -- which will probably be harder.

Regards,
Maciek


On Sun, Mar 3, 2013 at 7:31 PM, Lu Kai <fly...@gm...> wrote:

> Hi:
>   I am trying to install wxhaskell on Ubuntu and Win7, but I failed on
> both systems.
> Is there anyone who could solve either of my problem ?
> Thank you very much!
> My problem on ubuntu is as follows:
>
> My OS is : Ubuntu 12.04 I have install GHCI 7.4.1, and cabal 1.14.0 and I
> try to install wxHaskell to do some GUI programming. 1) I have installed
> the sudo apt-get install g++ sudo apt-get install libglu-dev sudo apt-get
> install libwxgtk2.8-dev
>
> 2) However, when I try to install wxhaskell using : cabal install wx
>
> I met a problem that:" Resolving dependencies... [1 of 1] Compiling Main (
> /tmp/wxc-0.90.0.4-9701/wxc-0.90.0.4/Setup.hs,
> /tmp/wxc-0.90.0.4-9701/wxc-0.90.0.4/dist/setup/Main.o ) Linking
> /tmp/wxc-0.90.0.4-9701/wxc-0.90.0.4/dist/setup/setup ... Configuring
> wxc-0.90.0.4...
>
> Warning: No config found to match: /usr/bin/wx-config --version=2.9
> --version-full in /usr/lib/i386-linux-gnu/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 cabal: Error: some packages failed to install: wx-0.90.0.1
> depends on wxc-0.90.0.4 which failed to install. wxc-0.90.0.4 failed during
> the configure step. The exception was: ExitFailure 1 wxcore-0.90.0.3
> depends on wxc-0.90.0.4 which failed to install. "
>
>
>
>
>
>
> For the Win7, my problem is : cabal install wx->
>
> Resolving dependencies...
>
> Configuring strict-0.3.2...
>
> Building strict-0.3.2...
>
> Preprocessing library strict-0.3.2...
>
> <built-in>:0:4: lexical error (UTF-8 decoding error)
>
> cabal: Error: some packages failed to install:
>
> strict-0.3.2 failed during the building phase. The exception was:
>
> ExitFailure 1
>
> wx-0.90.0.1 depends on strict-0.3.2 which failed to install.
>
> wxc-0.90.0.4 depends on strict-0.3.2 which failed to install.
>
> wxcore-0.90.0.3 depends on strict-0.3.2 which failed to install.
>
> wxdirect-0.90.0.1 depends on strict-0.3.2 which failed to install.
>
>
>
> Thanks a lot!
>
> Best!
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>
>

[wxhaskell-users] Question about how to install WxHakell on Ubuntu and Win7

[Lu K. <fly...@gm...>]

Hi:
  I am trying to install wxhaskell on Ubuntu and Win7, but I failed on both
systems.
Is there anyone who could solve either of my problem ?
Thank you very much!
My problem on ubuntu is as follows:

My OS is : Ubuntu 12.04 I have install GHCI 7.4.1, and cabal 1.14.0 and I
try to install wxHaskell to do some GUI programming. 1) I have installed
the sudo apt-get install g++ sudo apt-get install libglu-dev sudo apt-get
install libwxgtk2.8-dev

2) However, when I try to install wxhaskell using : cabal install wx

I met a problem that:" Resolving dependencies... [1 of 1] Compiling Main (
/tmp/wxc-0.90.0.4-9701/wxc-0.90.0.4/Setup.hs,
/tmp/wxc-0.90.0.4-9701/wxc-0.90.0.4/dist/setup/Main.o ) Linking
/tmp/wxc-0.90.0.4-9701/wxc-0.90.0.4/dist/setup/setup ... Configuring
wxc-0.90.0.4...

Warning: No config found to match: /usr/bin/wx-config --version=2.9
--version-full in /usr/lib/i386-linux-gnu/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 cabal: Error: some packages failed to install: wx-0.90.0.1
depends on wxc-0.90.0.4 which failed to install. wxc-0.90.0.4 failed during
the configure step. The exception was: ExitFailure 1 wxcore-0.90.0.3
depends on wxc-0.90.0.4 which failed to install. "






For the Win7, my problem is : cabal install wx->

Resolving dependencies...

Configuring strict-0.3.2...

Building strict-0.3.2...

Preprocessing library strict-0.3.2...

<built-in>:0:4: lexical error (UTF-8 decoding error)

cabal: Error: some packages failed to install:

strict-0.3.2 failed during the building phase. The exception was:

ExitFailure 1

wx-0.90.0.1 depends on strict-0.3.2 which failed to install.

wxc-0.90.0.4 depends on strict-0.3.2 which failed to install.

wxcore-0.90.0.3 depends on strict-0.3.2 which failed to install.

wxdirect-0.90.0.1 depends on strict-0.3.2 which failed to install.



Thanks a lot!

Best!