Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Mac::Carbon for Intel ... Done? 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • My PicTransfer app [*] uses Mac::Glue, and it's working perfectly as a Rosetta app right now, but I wonder if it'll get a speedup as a Universal binary. It's probably entirely I/O bound, so I doubt it. Anyway if you post another blog entry (or let me know) when you're done I'll try it when Mac::Glue comes out.

    [*] Used for transferring pics off removable media and launching an app (Capture One LE) when it's done. Let me know if you want a copy.
    • Rosetta? How'd you get that to work? I've never bothered trying, but when I run Mac::Carbon and Mac::Glue, they run in normal Mac space, not Rosetta space, and they don't work properly.

      Anyway, Mac::Glue is now uploaded! Let me know how it works for you.
      • Maybe I'm not testing any of the corner cases and it's just running in normal "mac" space and just working. I'm running as part of a .app (camelbones) if that makes any difference...

        Anyhow, I'll get around to testing the new Mac::Glue probably tomorrow.
        • In my experience, pretty much everything about Mac::Glue fails under Intel. But maybe wrapping it in a CamelBones app makes a difference, I don't know. Does CamelBones include the complete PPC perl interpreter and libraries and so on ... ?
          • Only if you make it. [perl.org] ;-)
            • Ah right!

              We did something like this for MacPerl, to distrbute apps. Called it ... RuntimeBuilder. You may want to borrow some of the code [macperl.com], which can help you identify which files you need to copy (not that it's hard, but it can be tedious). Most of the code there is actually saving the code inside the MacPerl droplet, so it may not be of much use. Plus, the paths are the Mac, not POSIX paths. So maybe it won't be of much use. :-)
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.