crosscompiling macports, how hard is it?

[Kevin Ballard]

In addition, the Mozilla project has a script (unfortunately I forget  
the exact name) which takes 2 single-architecture trees and combines  
them via lipo. It creates a new tree that contains all files that are  
the same in the 2 old trees. Any differing files that are binaries it  
combines via lipo. Any differing files that aren't binaries it tosses  
(can't do anything else with them), so you have to be careful in some  
projects (if, say, it builds a header file for distribution that  
changes per-architecture), but in general it works quite well.

On Jan 3, 2007, at 1:14 PM, Kevin Walzer wrote:

> 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 Ballard
http://kevin.sb.org
eridius at macports.org
http://www.tildesoft.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.macosforge.org/pipermail/macports-users/attachments/20070103/dc16177c/attachment.html