Universal Binaries

Kevin Ballard eridius at macports.org
Fri Feb 23 09:26:17 PST 2007

In general, building something with MacPorts and shipping it as part  
of an application is a risky business. I strongly recommend building  
the library yourself instead of relying on MacPorts to do it.

One example of this is the app HyperEdit. When the developer added  
the feature where HyperEdit can validate your HTML documents, he used  
the openjade port from MacPorts. Unfortunately this feature didn't  
work for anybody that didn't already have all of openjade's  
dependency's installed via MacPorts. I sent the author an email and  
he very quickly put out a new version that used the correct library  
linker paths to fix this problem.

On Feb 23, 2007, at 12:16 PM, Julian Yu-Chung Chen wrote:

> Say my application will build a library which statically link to  
> several libraries in MacPorts , so what I need is the universally  
> built library binary. Then my app can just bundle required UB libs.  
> What I can do now is using lipo to stitch intel and ppc binaries  
> together.

Kevin Ballard
eridius at macports.org

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

More information about the macports-users mailing list