From: Daniel G. <dg...@dc...> - 2009-11-11 14:44:29
|
Hi First of all, my apologies if this is not the correct list to report this. I had problems using the binary distribution of wxhaskell for OSX. I get an error message indicating that the post-install step failed because /opt/local/bin/ghc-pkg was not found. Since I'm not using the macports version of ghc anymore, it is not surprising that ghc-pkg was not found there. So I looked at /Volumes/wxhaskell/wxhaskell.pkg/Contents/Resources/ wxhaskell.post_install and saw this: #!/bin/sh GHCPKG=/opt/local/bin/ghc-pkg # try these versions of GHC-PKG in turn # would it maybe be best just to let the installer fail? if test "$GHCPKG" = ""; then if test -f /usr/local/bin/ghc-pkg; then GHCPKG=/usr/local/bin/ghc-pkg elif test -f /opt/local/bin/ghc-pkg; then GHCPKG=/opt/local/bin/ghc-pkg elif test -f /sw/bin/ghc-pkg; then GHCPKG=/sw/bin/ghc-pkg else echo "I can't find ghc-pkg in the path ($PATH)!" echo "Is GHC even installed?" exit 1 fi fi cat "$1/Contents/Resources/wxcore.pkg" | sed -e "s|\${wxhlibdir}|/usr/ local/wxhaskell/lib|" | $GHCPKG --global update - cat "$1/Contents/Resources/wx.pkg" | sed -e "s|\${wxhlibdir}|/usr/ local/wxhaskell/lib|" | $GHCPKG --global update - Now, since GHCPKG is initialized as "/opt/local/bin/ghc-pkg", the test "$GHCPKG" = "" will always fail. This means that the long chain of ifs is dead-code and, more importantly, this script is useless for anyone not using macports. This is particularly problematic now that the Haskell Platform is suggested as the main channel for ghc distribution. My suggestion would be to change the script to: #!/bin/sh GHCPKG=$(which ghc-pkg) # try these versions of GHC-PKG in turn # would it maybe be best just to let the installer fail? if test "$GHCPKG" = ""; then echo "I can't find ghc-pkg in the path ($PATH)!" echo "Is GHC even installed?" exit 1 fi cat "$1/Contents/Resources/wxcore.pkg" | sed -e "s|\${wxhlibdir}|/usr/ local/wxhaskell/lib|" | $GHCPKG --global update - cat "$1/Contents/Resources/wx.pkg" | sed -e "s|\${wxhlibdir}|/usr/ local/wxhaskell/lib|" | $GHCPKG --global update - Thanks, Daniel |
From: Eric Y. K. <eri...@gm...> - 2009-11-12 16:44:27
|
Hi Daniel, On Wed, Nov 11, 2009 at 11:17:23 -0300, Daniel Gorín wrote: > I had problems using the binary distribution of wxhaskell for OSX. I > get an error message indicating that the post-install step failed > because /opt/local/bin/ghc-pkg was not found. Since I'm not using the > macports version of ghc anymore, it is not surprising that ghc-pkg was > not found there. My suggestion : hang on for a little while, because the wxHaskell team is about to upload a new fully Cabal-based version of wxHaskell. This means that once you have wxWidgets (unfortunately, for MacOS X, you have to use a self-built one, for example via MacPorts) you can just cabal install wx or even any application that depends on wxHaskell and it will just work. Phew, things are really starting to come together : now that we have an easy way to create application bundles and an easy wxHaskell installation process, releasing GUI apps is going to be a lot easier. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 |
From: Daniel G. <dg...@dc...> - 2009-11-12 17:45:58
|
Hi Eric, Great to know. You should probably consider updating http://www.haskell.org/haskellwiki/WxHaskell/Building where binary releases are mentioned as the "official" way to install wxhaskell once this is done. Since we are on it, will the new cabalized version try to avoid the default wxwidgets installation on OSX? That is, for the case where wxhaskell is automatically pulled as a dependency.... Thanks, Daniel On Nov 12, 2009, at 1:44 PM, Eric Y. Kow wrote: > Hi Daniel, > > On Wed, Nov 11, 2009 at 11:17:23 -0300, Daniel Gorín wrote: >> I had problems using the binary distribution of wxhaskell for OSX. I >> get an error message indicating that the post-install step failed >> because /opt/local/bin/ghc-pkg was not found. Since I'm not using the >> macports version of ghc anymore, it is not surprising that ghc-pkg >> was >> not found there. > > My suggestion : hang on for a little while, because the wxHaskell team > is about to upload a new fully Cabal-based version of wxHaskell. This > means that once you have wxWidgets (unfortunately, for MacOS X, you > have > to use a self-built one, for example via MacPorts) you can just cabal > install wx or even any application that depends on wxHaskell and it > will > just work. > > Phew, things are really starting to come together : now that we have > an > easy way to create application bundles and an easy wxHaskell > installation process, releasing GUI apps is going to be a lot easier. > > -- > Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> > PGP Key ID: 08AC04F9 |