wxhaskell-users

[wxhaskell-users] making 'cabal install' just work for MacOS X gui apps

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

Hi everybody,

Attached are a Setup.hs file and a small addendum which you can use to
'cabal install' your wxHaskell apps on MacOS X without having to jump
through any extra hoops like calling the macosx-app script.

Note that the Setup.hs *should* be general enough to just work with your
application, and that it also tries to be clever enough not to do any of
these Mac-specific things outside of OS X.  But please let me know if
you run into any trouble.

Background on
 http://koweycode.blogspot.com/2009/09/cabal-installing-graphical-apps-on.html

Having this is an immense relief as far as scratching itches goes.
Hope it helps somebody else!

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9

Re: [wxhaskell-users] making 'cabal install' just work for MacOS X gui apps

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

Slightly improved version with chmod u+x (oops)

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9

Re: [wxhaskell-users] making 'cabal install' just work for MacOS X gui apps

[Andy G. <ha...@gi...>]

Hi Erik,

I started looking at/using this today, but I'm interested in building  
the app at _build_ time, not install time. My reason for this is that  
I'm developing under OS X, in an edit/build/run cycle, so I need  
the .app to be there for testing.

I started hacking on your Setup.hs to this end, but it occurred to me  
that this might be useful to others, in which case I should a) tidy up  
what I've done, b) keep the "build app on install" behaviour too, for  
deployers, c) test it across platforms and d) release it somehow.  But  
before I expend that effort, I wanted to ask if your version of Sep 11  
(http://www.mail-archive.com/wxh...@li.../msg00701.html 
) is the most current / best one to hack on.

Thanks!

-Andy

On 11 Sep 2009, at 21:04, Eric Y. Kow wrote:

> Slightly improved version with chmod u+x (oops)

Re: [wxhaskell-users] making 'cabal install' just work for MacOS X gui apps

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

Hi!

On Thu, Oct 15, 2009 at 15:29:43 +0100, Andy Gimblett wrote:
> I started hacking on your Setup.hs to this end, but it occurred to me  
> that this might be useful to others, in which case I should a) tidy up  
> what I've done, b) keep the "build app on install" behaviour too, for  
> deployers, c) test it across platforms and d) release it somehow.  But  
> before I expend that effort, I wanted to ask if your version of Sep 11  
> (http://www.mail-archive.com/wxh...@li.../msg00701.html 
> ) is the most current / best one to hack on.

Great.  I think the latest version can always be retrieved with

  wget http://code.haskell.org/GenI/Setup.hs

I sure wouldn't mind seeing some sort of Distribution.MacOSX module (or
whatever) being distributed on hackage.  I wonder if that would work
well with cabal-install, specifying something like appbundle == 0.1.* in
our Cabal files and having Setup.hs itself import a module from that
package.  It may be a good idea to follow up on this with the Cabal
folks...

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9

Re: [wxhaskell-users] making 'cabal install' just work for MacOS X gui apps

[Andy G. <ha...@gi...>]

Hi Eric (and all),

I've finally got round to looking at this again...

On 19 Oct 2009, at 13:20, Eric Y. Kow wrote:

> Great.  I think the latest version can always be retrieved with
>
>  wget http://code.haskell.org/GenI/Setup.hs

I've just taken this and put it into its own project on github:

http://github.com/gimbo/osxSetup.hs

> I sure wouldn't mind seeing some sort of Distribution.MacOSX module  
> (or
> whatever) being distributed on hackage.

What I've done so far is turn Setup.hs into Distribution/MacOSX.hs,  
and I'm about to start trying to work out how it would be called from  
a (simpler) Setup.hs, possibly in a nicely cross-platform manner.   
That probably means I need to join the cabal-devel list.

> I wonder if that would work
> well with cabal-install, specifying something like appbundle ==  
> 0.1.* in
> our Cabal files and having Setup.hs itself import a module from that
> package.  It may be a good idea to follow up on this with the Cabal
> folks...

If you've any suggestions, let me know.  I'll keep you informed as to  
progress.

Cheers!

-Andy

Re: [wxhaskell-users] making 'cabal install' just work for MacOS X gui apps

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

On Mon, Nov 09, 2009 at 15:57:02 +0000, Andy Gimblett wrote:
> I've just taken this and put it into its own project on github:
>
> http://github.com/gimbo/osxSetup.hs

Thanks!  You can count me in as a tester (after the upcoming Darcs Hacking
Sprint, at least).


> What I've done so far is turn Setup.hs into Distribution/MacOSX.hs, and 
> I'm about to start trying to work out how it would be called from a 
> (simpler) Setup.hs, possibly in a nicely cross-platform manner.  That 
> probably means I need to join the cabal-devel list.

I'm no Cabal or MacOS X expert, but it sounds like you could

1. get rid of main (put it in an example Setup.hs)

2. make appBundleHook take mRestrictTo and customiseAppBundle
   as parameters and remove them from the module.

3. make a more generic version of customiseAppBundle
   (note that I still don't know if all the steps there are
    really necessary; see GenI for the plist files, etc)

Otherwise, it looks like the Cabal file for, say, GenI could just depend on the
cabal-macosx package.

Hope this isn't already redundant with what you were planning,

Eric

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9