Hmm... well... that's the thing... I want to support Mac but I have no idea how to go about doing so.
I've built my Windows executable with PerlApp under the PDK, but I have an older release and can't afford the upgrade to support OS X* I have no idea how to go from "this works from the command line in Windows" to "this works by double-clicking a .app file on a Mac" -- none whatsoever. Everything I have read online or in books indicates I need to use XCode to put it all together. If not, though, I'd be perfectly happy to not. It's just that doing this stuff seems to be some of the *least* documented stuff ever anywhere. * ...not to mention the idea that ActiveState charges hundreds of dollars to perl developers to profiteer off of them when the stuff we put up for free on CPAN sells their product bugs the crap out of me. 2009/6/9 Eric Wilhelm <[email protected]> > # from Dodger > # on Monday 08 June 2009 21:40: > > >The web42 links I find do not work. > > > >Anyone know where it lives now? > > There's something resembling a fork of it under ExtUtils/MacMaker here. > > http://svn.scratchcomputing.com/Module-Build-Plugins-MacBundle/trunk/ > > I never did get that on the CPAN. The trouble with PerlWrapper was that > it didn't play nice with a cross-platform project. The above was my > take on making it feasible. See also the dotReader build code on the > CPAN. I could say more about it, but I would be reading the svn logs > and trying to remember where I left off almost 2 years ago. > > BTW, you don't really need to run an xcode project to build an > appbundle. If I were to dust it off, I would do something with just > the one binary (basically a miniperl with argv handling wedged into the > mac's `open` scheme) and drop the xcode part. > > --Eric > -- > Those who cannot remember the past are condemned to repeat it. > --George Santayana > --------------------------------------------------- > http://scratchcomputing.com > --------------------------------------------------- > -- Dodger
