-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dr. Ernie Prabhakar wrote:
I'd be interested! It would nice if we could figure out some way to semi-automate at least part of that process...
On Jan 2, 2007, at 11:06 PM, John Labovitz wrote:
I've successfully used a combination of lipo(1) and install_name_tool(1) to build universal versions of MacPorts libraries (built on separate PPC/Intel machines, alas) so that everything the app needed lived in <app>/Contents/Frameworks. I used install_name_tool to change any links to, eg, /opt/local so the linker would resolve them within the app bundle instead.
This was for a client, so I can't post the actual script, but if anyone's interested, I could probably write up a distilled version of what I did. It really wasn't very difficult.
--John _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Bob Ippolito's py2app package (which wraps up Python applications into standard Mac .app bundles) has a separate script/command-line tool called macho_standalone, which scans an app bundle and rewrites all the linker bits so that the dylibs in the app bundle are self-contained. It runs install_name_tool on them, IIRC. You may want to Google for "macho_standalone" to find the most recent version and documentation. - -- Kevin Walzer Code by Kevin http://www.codebykevin.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFm/KaEsLm8HXyq4sRAq/eAJ4tnru+dCc7StETLI1flV+idt96eQCfbOC8 adOjFMLMu+D2oOb559haXRw= =pf3U -----END PGP SIGNATURE-----