wxhaskell-users — General mailing list for wxhaskell users

[wxhaskell-users] ps re: mac OS installation help sought

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

PS addition to previous mail, another rather basic question:

ref  http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X

Step 3 says:
"Check your path to make sure you are using your wxWidgets and not the default Mac one"

I assume this means that $PATH should lead to my wxWidgets 2.9.3 library and not any other version,
and presumably the directories in $PATH are searched in the order in which they appear when shown 
by "echo $PATH". 
In my case this is:
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/Users/henrylockyer/Scala/bin:/usr/X11/bin


I have built wxWidgets in a directory under my user and from looking at the g++ commands issued, and 
also from trying to decrypt a little of one of the demo makefiles
". . .
wx_top_builddir = /Users/henrylockyer/wxWidgets/wxWidgets-2.9.3/build-cocoa-debug
. . .
LIBDIRNAME = $(wx_top_builddir)/lib
. . ."
                 from this I conclude I need the path to point to this directory:
/Users/henrylockyer/wxWidgets/wxWidgets-2.9.3/build-cocoa-debug/lib


But what should be included in the path? 
The directory containing 'lib' (ie. .../build-cocoa-debug),
or including the lib directory itself (ie. .../build-cocoa-debug/lib),
or something else?

Then, how to ensure my path is not leading to the "default Mac one"?
Taking a look for wx* in the PATH directories I find that they contain some things which look
suspiciously like they may relate to an earlier wxWidgets version (eg. "wxrc-2.8" below):

Henrys-iMac:~ henrylockyer$ ls /usr/bin/wx* /bin/wx*  /usr/sbin/wx*  /usr/local/bin/wx* 
ls: /bin/wx*: No such file or directory
ls: /usr/local/bin/wx*: No such file or directory
ls: /usr/sbin/wx*: No such file or directory
/usr/bin/wx-config		/usr/bin/wxPerl5.8.9		/usr/bin/wxperl_demo5.8.9.pl	/usr/bin/wxperl_overload5.8.9	/usr/bin/wxperl_xspp5.8.9
/usr/bin/wxPerl			/usr/bin/wxperl_demo.pl		/usr/bin/wxperl_overload	/usr/bin/wxperl_xspp		/usr/bin/wxrc
/usr/bin/wxPerl5.10.0		/usr/bin/wxperl_demo5.10.0.pl	/usr/bin/wxperl_overload5.10.0	/usr/bin/wxperl_xspp5.10.0	/usr/bin/wxrc-2.8

It seems to be mostly to do with 'wxperl', but:
- Is there in fact something here which will interfere with wxHaskell 0.9 / wxWidgets 2.9.3 in general ? 
- Is looking for things beginning with "wx" sufficient to find "the default Mac one" in the path?
- If the items listed are significant then what to do about them without causing other problems? 
- Include the wxWidgets 2.9.3 lib directory path into the first searched path file as the first searched path, ie. before /usr/bin ?

Thanks..
/ Henry 

[wxhaskell-users] mac OS installation help sought

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

Hi all
Looking for some help/advice about wxHaskell installation.
 
Hopefully appropriate to ask for basic help on this list (?)

It's for MacOS X 10.6.8 (Snow Leopard). 

I just upgraded GHC to 7.0.4, 64-bit option.

I'm not quite sure if I'm going down the right road.

A problem is I'm not experienced with building c++, or unix in general, and it's looking like there might be a fair bit of 
noise on this level in getting wxHaskell working.
Is it viable to try and use it if you are not experienced with compiling C++, make, libs etc. or should I give up now (hopefully not,
but I don't have as much time as I'd like to spend on it currently) ?  

I started the process with installing wxWidgets. I got 2.9.3 direct from wxWidgets.org, put the files in a dir under my user
and followed the downloaded instructions in "install.txt", under docs/osx, as follows:

  # Build the library for Cocoa (wxWidgets 2.9.0 and later) 
  mkdir build-cocoa-debug
  cd build-cocoa-debug
  ../configure --enable-unicode --enable-debug --disable-shared --with-osx_cocoa 
  make;cd ..
  # Build the samples and demos
  cd build-cocoa-debug/samples; make;cd ../..
  cd build-cocoa-debug/demos;   make;cd ../..

Lots of output to terminal - didn't try to wade through it all.. No obvious failure messages though saw some warnings.
I tried some of the widgets demo programs and samples and though much of it seemed to be working ok there were some odd aspects 
and things seemingly not working correctly but not sure if it was a problem with not very good samples/demos or the underlying install. 

(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" ).

Are these issues connected?  

Heinrich Apfelmus posted the following in response to the above github issue:

"The problem seems to be that QuickTime 7 is a 32bit library and will stay that way. Instead of porting it to 64bit, Apple chose to completely rewrite it instead, creating the QuickTime X library. You can still use the QuickTime 7 library, but only from 32bit processes.

Solution:

Install wxWidgets-devel-2.9.3 with the +universal flag on macports. This creates a library that is both 32bit and 64bit.
Configure GHC to produce and link 32bit binaries.
I don't know what exactly happens on the wxWidgets side, though. Do they link QuickTime when creating a 64bit target? "


Is there any further progress on this and is it an issue I need to resolve ?
I am not using macports. The configuration tool/script which seems to generate the makefiles amongst other things may accept
parameter for 'universal', I need to check further on the wxWidgets site, but is this what I need to do?

The configuration tool gives the following outputs amongst many others, is this relevant?
checking build system type... x86_64-apple-darwin10.8.0
checking host system type... x86_64-apple-darwin10.8.0
. . .

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? 

Can I go forward from where I am to go ahead and install whHask on top, or do I need to go back and fix wxWidgets?

If someone can help steer me here it would be much appreciated.  

Thanks/ Henry 

Re: [wxhaskell-users] debug-wx

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

Thanks Eric.  I'm hoping to instal wxHaskell this weekend, so it may well come in useful! 


On 1 Jun 2012, at 06:21, Eric Kow wrote:

> I've copied sample files from wxWidgets and wxHaskell repos into a kind of minimalistic debug-your-wxhaskell-setup resource
> 
> https://github.com/kowey/debug-wx
> 
> Wonder if it'd be useful for somebody to build something for wxc itself (we have wxWidgets, wxcore, wx)
> 
> -- 
> Eric Kow <http://erickow.com>
> 
> ------------------------------------------------------------------------------
> 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] debug-wx

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

I've copied sample files from wxWidgets and wxHaskell repos into a kind of minimalistic debug-your-wxhaskell-setup resource

https://github.com/kowey/debug-wx

Wonder if it'd be useful for somebody to build something for wxc itself (we have wxWidgets, wxcore, wx)

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

[wxhaskell-users] wxDateTime::TIME_T_FACTOR

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

Hey wxHaskellers,

Anybody know what to make of this?

dyld: Symbol not found: __ZN10wxDateTime13TIME_T_FACTORE
Referenced from: /Users/foo/Library/Haskell/ghc-7.0.4/lib/wxc-0.90.0.3/lib/libwxc.dylib
Expected in: flat namespace
in /Users/foo/Library/Haskell/ghc-7.0.4/lib/wxc-0.90.0.3/lib/libwxc.dylib
/Users/foo/Library/Haskell/bin/my-gui: line 2: 63052 Trace/BPT trap 

The wxHaskell instance was installed on MacOS X Snow Leopard, I think with the instructions on http://www.haskell.org/haskellwiki/WxHaskell/Mac

It's wxWidgets 2.9.3.1 installed via Homebrew.

Frustrating that this should *still* be a black art after all that hard work from Jeremy and others :-(

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

Re: [wxhaskell-users] Reducing linking and startup times (on Windows 7)

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

Hello,

I've noticed this too. For what I can gather, it's an issue with
wxwidgets 2.9 and/or wxcore-0.9, but I don't really have the time or
knowledge to debug it. It might have something to do with the build
configuration of 2.9. I built mine using these instructions.
http://www.haskell.org/haskellwiki/WxHaskell/2.9

when wx-0.13.2.1 (with wxwidgets 2.8) is used to build the examples,
the linking process takes few seconds at most and the programs start
instantly. I don't think there's any harm in using older version to
get started, but I'd like to know a solution for this too.

To install the old version I used wxPack binaries for 2.8 and
installed wxcore-0.13.2.1 separately. Env variables need to point to
all relevant wxwidgets2.8 files during compilation. Cabal install
wx-0.13.2.1 defaults to newest version of wxcore so you need to:

cabal unpack  wx-0.13.2.1 (creates a folder inside the folder you're at)
cd wx-0.13.2.1
edit wx.cabal to target wxcore-0.13.2.1 specifically (rather self
explanatory I think)
runhaskell.exe Setup.lhs configure
runhaskell.exe Setup.lhs build
runhaskell.exe Setup.lhs install

This might not be exactly correct. I'm just swinging from memory. When
compiling the applications, use wx-0.13.2.1 instead of wx.


Antton Tapani

On Fri, May 25, 2012 at 4:18 PM, Fabian Binz <fab...@ya...> wrote:
> Hello everyone,
>
>
>
> is there a way to reduce linking and startup times?  Linking a “Hello
> World”-like wxHaskell program takes about 45 seconds and starting it up
> about
>
> 5. While the former is still acceptable I guess, the latter is way too long.
>
>
> Regards,
>
> Fabian
>
>
> ------------------------------------------------------------------------------
> 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] Reducing linking and startup times (on Windows 7)

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

Hello everyone,

 

is there a way to reduce linking and startup times?  Linking a "Hello
World"-like wxHaskell program takes about 45 seconds and starting it up
about 

5. While the former is still acceptable I guess, the latter is way too long.


Regards, 

Fabian

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

[Jeremy O'D. <jer...@gm...>]

Hi Hiratara,

On 22 May 2012 04:22, Honma Masahiro <hir...@gm...> wrote:

> I'm a Japanese programer and apologize for my poor broken English :(
>

Much better than my non-existant Japanese :-)


> 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.
>
>
> % ghc -package wx -o helloworld HelloWorld.hs
> Linking helloworld ...
> ld: warning: ignoring file
> /System/Library/Frameworks//QuickTime.framework/QuickTime, file was
> built for unsupported file format which is not the architecture being
> linked (x86_64)
> ld: warning: could not create compact unwind for _ffi_call_unix64:
> does not use RBP or RSP based frame
>

This is a link issue with multimedia on Lion. It seems that Quicktime is a
32 bit library only. You can ignore this.


> Undefined symbols for architecture x86_64:
>  "_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)
>  "_wxListItemAttr_Create", referenced from:
>
>  _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_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)
>  "_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_SetTextColour", referenced from:
>      _s15xV_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)
>  "_wxListItemAttr_SetBackgroundColour", referenced from:
>      _s15Gu_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_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_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)
>  "_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_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)
>  "_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)
>  "_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)
>  "_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)
>  "_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)
>  "_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)
>  "_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)
> ld: symbol(s) not found for architecture x86_64
> collect2: ld returned 1 exit status
>

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.


> What should I do to fix these errors?
>
> I built ghc and wxWidgets by following steps;
>
> % brew install haskell-platform
>  (version: 2011.4.0.0)
> % cabal update
> % cabal install llvm
>  (version: 3.0.1.0)
> % brew install wxmac --use-llvm --devel
>  (version: 2.9.3.1)
> % cabal install wx cabal-macosx
>  (version: 0.90.0.1 and 0.2.2)
> % ghc -package wx -o helloworld HelloWorld.hs
>  (I got errors described above.)
>
> $ ghc `wx-config --libs` -package wx -o helloworld HelloWorld.hs
>  (I also tried this commnad, but I got the same result.)
>

These steps look correct to me.


> Then, I also try to compile hworld.cpp by using wxWidgets.
> I got warnings below, but I could run ./hworld .
>
> % g++ hworld.cpp `wx-config --libs` `wx-config --cxxflags` -o hworld
> ld: warning: ignoring file
> /System/Library/Frameworks//QuickTime.framework/QuickTime, file was
> built for unsupported file format which is not the architecture being
> linked (x86_64)
>

This is the C++ version of the warning that Quicktime is a 32 bit
framework, and cannot be linked to a  64 bit binary. Again, you can ignore
this (it needs to be fixed in wxWidgets).

Best regards
Jeremy

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

[Honma M. <hir...@gm...>]

Hi,

I'm a Japanese programer and apologize for my poor broken English :(

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.


% ghc -package wx -o helloworld HelloWorld.hs
Linking helloworld ...
ld: warning: ignoring file
/System/Library/Frameworks//QuickTime.framework/QuickTime, file was
built for unsupported file format which is not the architecture being
linked (x86_64)
ld: warning: could not create compact unwind for _ffi_call_unix64:
does not use RBP or RSP based frame
Undefined symbols for architecture x86_64:
  "_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)
  "_wxListItemAttr_Create", referenced from:
      _wxcorezm0zi90zi0zi1_GraphicsziUIziWXCoreziWxcClassesAL_listItemAttrCreate1_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)
  "_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_SetTextColour", referenced from:
      _s15xV_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)
  "_wxListItemAttr_SetBackgroundColour", referenced from:
      _s15Gu_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_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_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)
  "_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_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)
  "_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)
  "_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)
  "_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)
  "_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)
  "_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)
  "_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)
ld: symbol(s) not found for architecture x86_64
collect2: ld returned 1 exit status


What should I do to fix these errors?

I built ghc and wxWidgets by following steps;

% brew install haskell-platform
  (version: 2011.4.0.0)
% cabal update
% cabal install llvm
  (version: 3.0.1.0)
% brew install wxmac --use-llvm --devel
  (version: 2.9.3.1)
% cabal install wx cabal-macosx
  (version: 0.90.0.1 and 0.2.2)
% ghc -package wx -o helloworld HelloWorld.hs
  (I got errors described above.)

$ ghc `wx-config --libs` -package wx -o helloworld HelloWorld.hs
  (I also tried this commnad, but I got the same result.)


Then, I also try to compile hworld.cpp by using wxWidgets.
I got warnings below, but I could run ./hworld .

% g++ hworld.cpp `wx-config --libs` `wx-config --cxxflags` -o hworld
ld: warning: ignoring file
/System/Library/Frameworks//QuickTime.framework/QuickTime, file was
built for unsupported file format which is not the architecture being
linked (x86_64)


Regards,
hiratara

[wxhaskell-users] mail archive and xrc

[Graham B. <gr...@fa...>]

Stupid question number one :) Can you search the mail archive ? I couldn't see anything offhand.

Also can you use xrc ? On the wiki news section says yes, short guide says no.
If you can does anyone have any examples ?

Thanks
Graham

Re: [wxhaskell-users] virtual list control

[Jeremy O'D. <jer...@gm...>]

Hi Fabian,

On 12 May 2012 16:12, Fabian Binz <fab...@ya...> wrote:

>   Hi Jeremy, ****
>
> I don't know if you continued working on this, but I forked wxHaskell on
> GitHub and tried to implement it myself:
> https://github.com/FabianBinz/wxHaskell
>
I have been doing some work, but I don't have a lot of time right now, so
it is going more slowly than I would like.

> For testing purposes, I only implemented the OnGetItemText and
> SetItemCount method and it seems to work.
>
> To implement the "virtual" list control, I defined a new class
> wxVirtualListCtrl in wxc:****
>
>
> https://github.com/FabianBinz/wxHaskell/blob/master/wxc/src/include/virtuallistctrl_impl.h
> ****
>
> Since it needs to invoke a callback function, I created the typedef
> OnGetItemTextCallback. To make wxdirect accept this new type, I extended
> the parser (patomtype) in ParseC.hs. This solution is very ad-hoc and I
> think because wxc is supposed to be a language agnostic C wrapper, we
> should maybe add another macro to wcx_types.hs (something like TCallback),
> which is then recognized by wxdirect.****
>
> So, while this all works pretty well, there is unfortunately a memory leak
> in Graphics.UI.WXCore.VirtualListCtrl, because of my use of newCString. At
> the moment I don't know how to fix it and would be glad if someone could
> give me some advice.
>

You need to use a finalizer - this is what I am looking into. There is an
overview at
http://www.haskell.org/haskellwiki/GHC/Using_the_FFI#Calling_Haskell_from_C,
but it could be clearer! Basic idea is that you free the CString when the
GC has no more references to the closure in which it is used.

I am using the event handler code as a model, since this already allows
callbacks from C to Haskell, and handles reference counting. Just haven't
finished yet.

I will take a look at your fork and see if you are further along than me,
and take code accordingly.

Best regards
Jeremy

Re: [wxhaskell-users] virtual list control

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

Hi Jeremy, 

 

I don't know if you continued working on this, but I forked wxHaskell on
GitHub and tried to implement it myself:
https://github.com/FabianBinz/wxHaskell

 

 

For testing purposes, I only implemented the OnGetItemText and SetItemCount
method and it seems to work. 

 

 

To implement the "virtual" list control, I defined a new class
wxVirtualListCtrl in wxc:

https://github.com/FabianBinz/wxHaskell/blob/master/wxc/src/include/virtuall
istctrl_impl.h

 

 

Since it needs to invoke a callback function, I created the typedef
OnGetItemTextCallback. To make wxdirect accept this new type, I extended the
parser (patomtype) in ParseC.hs. This solution is very ad-hoc and I think
because wxc is supposed to be a language agnostic C wrapper, we should maybe
add another macro to wcx_types.hs (something like TCallback), which is then
recognized by wxdirect.

 

 

So, while this all works pretty well, there is unfortunately a memory leak
in Graphics.UI.WXCore.VirtualListCtrl, because of my use of newCString. At
the moment I don't know how to fix it and would be glad if someone could
give me some advice.

 

 

 

Regards,

Fabian

 

Re: [wxhaskell-users] Using wxHaskell on Mac OS x

[Jeremy O'D. <jer...@gm...>]

On 24 April 2012 12:52, Eric Kow <eri...@gm...> wrote:

>
> /me roots for Nix
>

Which currently doesn't build :-(

See https://github.com/jodonoghue/wxHaskell/issues/4 - I'm working on it,
but will not be able to test the solution as life is too short to create
Yet Another Test Environment - I already test on the following (the top 3
get the most love):

   - Mac OS X Lion (64bit GHC / 64 bit wxWidgets 2.9.3 / wxHaskell 0.90)
   - Windows 7 Enterprise (64bit OS / 32 bit GHC / 32 bit wxWidgets 2.9.3 /
   wxHaskell 0.90) in a VM
   - Debian 6 (32 bit OS / 32 bit GHC / 32 bit wxWidgets 2.9.3 / wxHaskell
   0.90) in a VM
   - FreeBSD (32 bit OS / 32 bit GHC / 32 bit wxWidgets 2.8.12 / wxHaskell
   0.13) in a VM

That's enough for anyone with other things to do, I'm afraid.

Jeremy

Re: [wxhaskell-users] wxHaskell 0.90 on Windows 7?

[Jeremy O'D. <jer...@gm...>]

Thanks Antton. I will update the wiki build instructions.

Jeremy

On 24 April 2012 13:08, Antton Tapani <ant...@gm...> wrote:

> Hey,
>
> I got the same error at first too. Running
> set LANG=C
> in cmd before compiling fixed it for me. This is probably not
> common/default behavior since no one has considred it important to
> mention it in the guides. Only info I was able to find on this was
> from a japanese blog using google translate.
>
> On Tue, Apr 24, 2012 at 2:32 PM, carlos gomez <car...@gm...>
> wrote:
> > Hello, I'm trying to build wxhaskell on windows 7 and HP.2011.4.0.0,
> > but I've got this error when installing wxdirect:
> >
> > C:\>cabal install wxdirect
> > Resolving dependencies...
> > Configuring strict-0.3.2...
> > Preprocessing library strict-0.3.2...
> > Building strict-0.3.2...
> >
> > <interno>:0:5: 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
> > wxdirect-0.90.0.1 depends on strict-0.3.2 which failed to install.
> >
> >
> > Any ideas of what to do?
> >
> > thanks, Carlos Gomez
> >
> >
> > On 22 April 2012 09:48, Eric Kow <eri...@gm...> wrote:
> >>
> >> Hi,
> >>
> >> After struggling a bit to get wxHaskell 0.90 working on a Windows VM, I
> >> thought a few links and tips could be useful
> >>
> >> http://www.haskell.org/haskellwiki/WxHaskell/Windows
> >>
> >> --
> >> Eric Kow <http://erickow.com>
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> For Developers, A Lot Can Happen In A Second.
> >> Boundary is the first to Know...and Tell You.
> >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> >> http://p.sf.net/sfu/Boundary-d2dvs2
> >> _______________________________________________
> >> wxhaskell-users mailing list
> >> wxh...@li...
> >> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > 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
> >
>
>
> ------------------------------------------------------------------------------
> 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] wxHaskell 0.90 on Windows 7?

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

Hey,

I got the same error at first too. Running
set LANG=C
in cmd before compiling fixed it for me. This is probably not
common/default behavior since no one has considred it important to
mention it in the guides. Only info I was able to find on this was
from a japanese blog using google translate.

On Tue, Apr 24, 2012 at 2:32 PM, carlos gomez <car...@gm...> wrote:
> Hello, I'm trying to build wxhaskell on windows 7 and HP.2011.4.0.0,
> but I've got this error when installing wxdirect:
>
> C:\>cabal install wxdirect
> Resolving dependencies...
> Configuring strict-0.3.2...
> Preprocessing library strict-0.3.2...
> Building strict-0.3.2...
>
> <interno>:0:5: 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
> wxdirect-0.90.0.1 depends on strict-0.3.2 which failed to install.
>
>
> Any ideas of what to do?
>
> thanks, Carlos Gomez
>
>
> On 22 April 2012 09:48, Eric Kow <eri...@gm...> wrote:
>>
>> Hi,
>>
>> After struggling a bit to get wxHaskell 0.90 working on a Windows VM, I
>> thought a few links and tips could be useful
>>
>> http://www.haskell.org/haskellwiki/WxHaskell/Windows
>>
>> --
>> Eric Kow <http://erickow.com>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> For Developers, A Lot Can Happen In A Second.
>> Boundary is the first to Know...and Tell You.
>> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
>> http://p.sf.net/sfu/Boundary-d2dvs2
>> _______________________________________________
>> wxhaskell-users mailing list
>> wxh...@li...
>> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>>
>
>
> ------------------------------------------------------------------------------
> 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] Using wxHaskell on Mac OS x

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

On 24 Apr 2012, at 12:15, Heinrich Apfelmus wrote:
> Both these issues can be avoided by using homebrew. Whether this merely 
> trades them for other issues is another question, of course...

I'll add that whatever you choose to do, I'll add that it's probably a good idea to stick to one package manager and not try to combine them (this is pure superstitious thinking on my part, however).

That said, when I first switched, I used both for a while until MacPorts usage withered away.

Not pushing either way.

/me roots for Nix

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

Re: [wxhaskell-users] wxHaskell 0.90 on Windows 7?

[carlos g. <car...@gm...>]

Hello, I'm trying to build wxhaskell on windows 7 and HP.2011.4.0.0,
but I've got this error when installing wxdirect:

C:\>cabal install wxdirect
Resolving dependencies...
Configuring strict-0.3.2...
Preprocessing library strict-0.3.2...
Building strict-0.3.2...

<interno>:0:5: 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
wxdirect-0.90.0.1 depends on strict-0.3.2 which failed to install.


Any ideas of what to do?

thanks, Carlos Gomez


On 22 April 2012 09:48, Eric Kow <eri...@gm...> wrote:

> Hi,
>
> After struggling a bit to get wxHaskell 0.90 working on a Windows VM, I
> thought a few links and tips could be useful
>
> http://www.haskell.org/haskellwiki/WxHaskell/Windows
>
> --
> Eric Kow <http://erickow.com>
>
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users
>
>

Re: [wxhaskell-users] Using wxHaskell on Mac OS x

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

Andrew Butterfield wrote:
> 
> $ ghc --make -package wx HelloWorld.hs 
> [2 of 2] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
> Linking HelloWorld ...
> ld: warning: in /opt/local/lib/libwx_osx_cocoau_xrc-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
> ld: warning: in /opt/local/lib/libwx_osx_cocoau_webview-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
>  [..]
> Undefined symbols:
>   "_iconv_open", referenced from:
>       _hs_iconv_open in libHSbase-4.3.1.0.a(iconv.o)
>      (maybe you meant: _hs_iconv_open)
>   "_locale_charset", referenced from:
>       _localeEncoding in libHSbase-4.3.1.0.a(PrelIOUtils.o)
>   "_iconv", referenced from:
>       _hs_iconv in libHSbase-4.3.1.0.a(iconv.o)
>      (maybe you meant: _hs_iconv_open, _hs_iconv , _hs_iconv_close )
>   "_iconv_close", referenced from:
>       _hs_iconv_close in libHSbase-4.3.1.0.a(iconv.o)
>      (maybe you meant: _hs_iconv_close)
> ld: symbol(s) not found
> collect2: ld returned 1 exit status
> 
> [~/Documents/wxOnMacOSX]
> $

Yay, I know what's going on!

* The first error messages indicate that GHC complains about your 
wxWidgets installation being 32bit. This means that you have a 64bit 
GHC. The solution is to install the wxWidgets library with the 
+universal flag, i.e.

     sudo port install wxWidgets-devel +universal

It might be that you have to do the same with the dependencies of the 
wxWidgets-devel port. You can set the +universal flag globally in

     /opt/local/etc/macports/variants.conf

* The undefined symbols are due to two different libiconv, one provided 
by OS X and one provided by Macports. The solution is to tell GHC to 
prefer the former

     ghc --make -package wx HelloWorld.hs -L/usr/lib


Both these issues can be avoided by using homebrew. Whether this merely 
trades them for other issues is another question, of course...


Concerning the EnableGUI thing, it will be obsolete very soon. I have 
submitted a patch to Jeremy who will upload a new version to hackage 
once he has tested all platforms.


Best regards,
Heinrich Apfelmus

--
http://apfelmus.nfshost.com

Re: [wxhaskell-users] Using wxHaskell on Mac OS x

[Andrew B. <and...@cs...>]

Thanks Eric,
  I have a proposal to help in this regard, just sent to wxhaskell-devel


On 24 Apr 2012, at 09:15, Eric Kow wrote:

> 
> 
> What's your architecture? If 64 bit, what sort of GHC do you have?

My Mac: 10.6.8, Intel Core i7

 System Version:	Mac OS X 10.6.8 (10K549)
  Kernel Version:	Darwin 10.8.0
  Boot Volume:	Macintosh HD
  Boot Mode:	Normal
  Computer Name:	Andrew Butterfield’s iMac
  User Name:	Andrew Butterfield (andrewbutterfield)
  Secure Virtual Memory:	Not Enabled
  64-bit Kernel and Extensions:	No
  Time since boot:	1 day44 minutes

I guess thats 32bit, then...

GHCi, version 7.0.4: http://www.haskell.org/ghc/  :? for help
> 
> I personally threw my hands up a couple of years ago and ended up switching to HomeBrew (see http://permalink.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/908 )

I switched as well, but had no better luck...

> 

--------------------------------------------------------------------
Andrew Butterfield     Tel: +353-1-896-2517     Fax: +353-1-677-2204
Lero@TCD, Head of Foundations & Methods Research Group
Director of Teaching and Learning - Undergraduate,
School of Computer Science and Statistics,
Room G.39, O'Reilly Institute, Trinity College, University of Dublin
                          http://www.scss.tcd.ie/Andrew.Butterfield/
--------------------------------------------------------------------

Re: [wxhaskell-users] Using wxHaskell on Mac OS x

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

On 24 Apr 2012, at 08:40, Andrew Butterfield wrote:

> 
> On 23 Apr 2012, at 23:47, Eric Kow wrote:
> 
>> I'm a bit confused by this. Isn't /opt/local used by Macports rather than Homebrew?
>> also, does non-ghci stuff work?
> 
> Apologies - it was MacPorts  - I was getting hopelessly confused at this stage ..

That's our fault! :-)
We do need to work on making this sort of stuff easier to understand.

One mild annoyance being that Haskell wiki doesn't give a separate colour

> ld: warning: in /opt/local/lib/libwx_baseu-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
> ld: warning: in /opt/local/lib/libiconv.dylib, file was built for unsupported file format which is not the architecture being linked (i386)

What's your architecture? If 64 bit, what sort of GHC do you have?

> Undefined symbols:
>   "_iconv_open", referenced from:
>       _hs_iconv_open in libHSbase-4.3.1.0.a(iconv.o)
>      (maybe you meant: _hs_iconv_open)
>   "_locale_charset", referenced from:
>       _localeEncoding in libHSbase-4.3.1.0.a(PrelIOUtils.o)
>   "_iconv", referenced from:
>       _hs_iconv in libHSbase-4.3.1.0.a(iconv.o)
>      (maybe you meant: _hs_iconv_open, _hs_iconv , _hs_iconv_close )
>   "_iconv_close", referenced from:
>       _hs_iconv_close in libHSbase-4.3.1.0.a(iconv.o)
>      (maybe you meant: _hs_iconv_close)
> ld: symbol(s) not found
> collect2: ld returned 1 exit status

I notice apfelmus mentioned that he'd tweaked the Portfile for wxWidgets.
Comments?

I personally threw my hands up a couple of years ago and ended up switching to HomeBrew (see http://permalink.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/908 )

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

Re: [wxhaskell-users] Using wxHaskell on Mac OS x

[Andrew B. <and...@cs...>]

On 23 Apr 2012, at 23:47, Eric Kow wrote:

> I'm a bit confused by this. Isn't /opt/local used by Macports rather than Homebrew?
> also, does non-ghci stuff work?

Apologies - it was MacPorts  - I was getting hopelessly confused at this stage ..

If I try to compile HelloWorld.hs I get the error below

It seems clear that I need to identify and inform the build process about my architecture

However there are no clear instructions on the wiki on how to do this

(PS - I am having equal  difficulties build wxH 0.9 on wxW 2.9.3  on 64bit windows.... - but that's for another email)


$ ghc --make -package wx HelloWorld.hs 
[2 of 2] Compiling Main             ( HelloWorld.hs, HelloWorld.o )
Linking HelloWorld ...
ld: warning: in /opt/local/lib/libwx_osx_cocoau_xrc-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_webview-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_stc-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_richtext-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_ribbon-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_propgrid-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_aui-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_gl-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_html-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_qa-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_adv-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_osx_cocoau_core-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_baseu_xml-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_baseu_net-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libwx_baseu-2.9.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
ld: warning: in /opt/local/lib/libiconv.dylib, file was built for unsupported file format which is not the architecture being linked (i386)
Undefined symbols:
  "_iconv_open", referenced from:
      _hs_iconv_open in libHSbase-4.3.1.0.a(iconv.o)
     (maybe you meant: _hs_iconv_open)
  "_locale_charset", referenced from:
      _localeEncoding in libHSbase-4.3.1.0.a(PrelIOUtils.o)
  "_iconv", referenced from:
      _hs_iconv in libHSbase-4.3.1.0.a(iconv.o)
     (maybe you meant: _hs_iconv_open, _hs_iconv , _hs_iconv_close )
  "_iconv_close", referenced from:
      _hs_iconv_close in libHSbase-4.3.1.0.a(iconv.o)
     (maybe you meant: _hs_iconv_close)
ld: symbol(s) not found
collect2: ld returned 1 exit status

[~/Documents/wxOnMacOSX]
$ 


> 
> On Monday, 23 April 2012, Andrew Butterfield wrote:
> I've done yet another attempt at installing wxHaskell on Mac OS X (Intel, Snow Leopard)
> following the page at 
> 
>  http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X
> 
> I setup ghc 7.0.4
> I did brew install wxmac --devel
> 
> I am then asked to check my path to make sure I am using  "my" wxWidgets and not the default one
> 
> (I had deleted an old reference to wx 2.8 - now my path does not mention wxwidgets at all)
> 
> wx2.9.3 was installed by homebrew in /opt/local/.... but I had no idea what to put in my path
> (A question to stackoverflow got a completely useless answer....)
> 
> So I decided to soldier on...
>   I did   cabal install wx cabal-macosx   --- waited - all installed just fine - it seemed
> to have picked up all the stuff installed by brew.
> 
> I then got the EnableGUI module as described lower down the page
> it compiled fine
> I then edited HelloWord.hs to import it
> ,and then started ghci as recommended
> 
> 
> -- 
> Eric Kow <http://erickow.com>
> PGP Key ID: 08AC04F9
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> wxhaskell-users mailing list
> wxh...@li...
> https://lists.sourceforge.net/lists/listinfo/wxhaskell-users

--------------------------------------------------------------------
Andrew Butterfield     Tel: +353-1-896-2517     Fax: +353-1-677-2204
Lero@TCD, Head of Foundations & Methods Research Group
Director of Teaching and Learning - Undergraduate,
School of Computer Science and Statistics,
Room G.39, O'Reilly Institute, Trinity College, University of Dublin
                          http://www.scss.tcd.ie/Andrew.Butterfield/
--------------------------------------------------------------------

Re: [wxhaskell-users] Using wxHaskell on Mac OS x

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

I'm a bit confused by this. Isn't /opt/local used by Macports rather than
Homebrew?
also, does non-ghci stuff work?

On Monday, 23 April 2012, Andrew Butterfield wrote:

> I've done yet another attempt at installing wxHaskell on Mac OS X (Intel,
> Snow Leopard)
> following the page at
>
>  http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X
>
> I setup ghc 7.0.4
> I did brew install wxmac --devel
>
> I am then asked to check my path to make sure I am using  "my" wxWidgets
> and not the default one
>
> (I had deleted an old reference to wx 2.8 - now my path does not mention
> wxwidgets at all)
>
> wx2.9.3 was installed by homebrew in /opt/local/.... but I had no idea
> what to put in my path
> (A question to stackoverflow got a completely useless answer....)
>
> So I decided to soldier on...
>   I did   cabal install wx cabal-macosx   --- waited - all installed just
> fine - it seemed
> to have picked up all the stuff installed by brew.
>
> I then got the EnableGUI module as described lower down the page
> it compiled fine
> I then edited HelloWord.hs to import it
> ,and then started ghci as recommended
>


-- 
Eric Kow <http://erickow.com>
PGP Key ID: 08AC04F9

[wxhaskell-users] wxHaskell 0.90 still not working on Windows XP

[Rene de V. <ren...@ho...>]

Hello,
I suspect something went wrong when building something...
ghc-pkg describe wxc 
gives this:
library-dirs: C:\other\bin C:\ghc\ghc-7.4.1\mingw\lib              C:\other\wxWidgets-2.9.3\lib\gcc_dllhs-libraries:extra-libraries: uuid wxmsw29u_xrc wxmsw29u_stc wxmsw29u_richtext                 wxmsw29u_ribbon wxmsw29u_propgrid wxmsw29u_webview wxmsw29u_aui                 wxmsw29u_gl wxmsw29u_media wxmsw29u_html wxmsw29u_adv wxmsw29u_core                 wxbase29u_xml wxbase29u_net wxbase29u wxtiff wxjpeg wxpng wxzlib                 wxregexu wxexpat opengl32 glu32 kernel32 user32 gdi32 comdlg32                 wxregexu winspool winmm shell32 comctl32 ole32 oleaut32 uuid rpcrt4                 advapi32 wsock32extra-ghci-libraries:include-dirs: C:\other\wxWidgets-2.9.3\include              C:\other\wxWidgets-2.9.3\lib\gcc_dll\mswu              "C:\\Dokumente und Einstellungen\\Rene\\Anwendungsdaten\\cabal\\wxc-0.90.0.2\\ghc-7.4.1\\include"includes:depends: base-4.5.0.0-597748f6f53a7442bcae283373264bb6         wxdirect-0.90.0.1-6ac67ae0372ee1a7703691afae80d181hugs-options:cc-options:ld-options:framework-dirs:frameworks:

Can someone send the same output of a working wxHaskell ?
Attempting to use ghci gives me
Loading package wxc-0.90.0.2 ... ghc.exe: panic! (the 'impossible' happened)  (GHC version 7.4.1 for i386-unknown-mingw32):	loadArchive "C:\\other\\wxWidgets-2.9.3\\lib\\gcc_dll\\libwxmsw29u_xrc.a": failed
The error comes because ghci cannot handle the .data$4 section into the above archive library.
I am not even sure why the attempt is being made to load the above file. I don't see any dependencies to it in the DLL's.
Rene.
 		 	   		  

[wxhaskell-users] Using wxHaskell on Mac OS x

[Andrew B. <and...@cs...>]

I've done yet another attempt at installing wxHaskell on Mac OS X (Intel, Snow Leopard)
following the page at 

 http://www.haskell.org/haskellwiki/WxHaskell/MacOS_X

I setup ghc 7.0.4
I did brew install wxmac --devel

I am then asked to check my path to make sure I am using  "my" wxWidgets and not the default one

(I had deleted an old reference to wx 2.8 - now my path does not mention wxwidgets at all)

wx2.9.3 was installed by homebrew in /opt/local/.... but I had no idea what to put in my path
(A question to stackoverflow got a completely useless answer....)

So I decided to soldier on...
  I did   cabal install wx cabal-macosx   --- waited - all installed just fine - it seemed
to have picked up all the stuff installed by brew.

I then got the EnableGUI module as described lower down the page
it compiled fine
I then edited HelloWord.hs to import it
,and then started ghci as recommended

I get the error

Loading package wxc-0.90.0.2 ... can't load .so/.DLL for: wx_baseu-2.9 (dlopen(/opt/local/lib/libwx_baseu-2.9.dylib, 9): no suitable image found.  Did find:
	/opt/local/lib/libwx_baseu-2.9.dylib: mach-o, but wrong architecture)


How do I fix this?

--------------------------------------------------------------------
Andrew Butterfield     Tel: +353-1-896-2517     Fax: +353-1-677-2204
Lero@TCD, Head of Foundations & Methods Research Group
Director of Teaching and Learning - Undergraduate,
School of Computer Science and Statistics,
Room G.39, O'Reilly Institute, Trinity College, University of Dublin
                          http://www.scss.tcd.ie/Andrew.Butterfield/
--------------------------------------------------------------------

[wxhaskell-users] wxHaskell 0.90 on Windows 7?

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

Hi,

After struggling a bit to get wxHaskell 0.90 working on a Windows VM, I thought a few links and tips could be useful

http://www.haskell.org/haskellwiki/WxHaskell/Windows

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