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
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
