Menu
▾
▴
wxhaskell-users
|
From: luc t. <luc...@gm...> - 2013-03-19 00:04:53
|
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) |
|
From: Eric K. <eri...@gm...> - 2013-03-19 14:38:00
|
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> |
|
From: Luc T. <luc...@gm...> - 2013-03-19 14:59:54
|
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> > > |
|
From: Luc T. <luc...@gm...> - 2013-03-19 15:19:51
|
>- 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> > > |
|
From: Eric K. <eri...@gm...> - 2013-03-19 15:55:50
|
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> |
|
From: Luc T. <luc...@gm...> - 2013-03-19 16:15:48
|
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>
>
>
|
|
From: Luc T. <luc...@gm...> - 2013-03-19 16:19:00
|
How can I make sure all is cleaned before I install a 64 platform ? i.e. no 32 residue ? any way to clean , automated ? |
|
From: Eric K. <eri...@gm...> - 2013-03-19 16:21:20
|
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> |
|
From: Luc T. <luc...@gm...> - 2013-03-19 20:32:18
|
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> > > |
|
From: Eric K. <eri...@gm...> - 2013-03-20 09:58:30
|
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> |
|
From: Luc T. <luc...@gm...> - 2013-03-20 10:48:43
|
>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> > > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X