Universal Binaries

[Julian Yu-Chung Chen]

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.

my .2 cents
--
Julian Yu-Chung Chen
julian at evl.uic.edu


On Feb 23, 2007, at 9:35 AM, Kevin Ballard wrote:

> I'm curious as to why you want universal binaries. In general,  
> binaries produced via MacPorts can't be copied between platforms,  
> as they need all the libraries they depend on. Sure, you can copy  
> your entire MacPorts /opt/local tree, but outside of doing that  
> it's quite hard to migrate the built products.
>
> Given that, what benefit do you get from universal binaries?
>
> On Feb 22, 2007, at 5:23 PM, Ryan Schmidt wrote:
>
>> On Feb 22, 2007, at 02:35, Nathan Brazil wrote:
>>
>>> Hi.  Is it possible to produce universal binaries from MacPorts?   
>>> For example, are the GTK+ binaries produced from MacPorts  
>>> specific to the architecture of the machine it is produced on  
>>> (PPC vs Intel), or is there a way to produce binaries that will  
>>> work natively on both?
>>
>> MacPorts produces platform-native binaries. There is no way to  
>> produce universal binaries. For many projects, it is a simple  
>> matter to produce universal binaries. However, some projects need  
>> to be handled specially, so MacPorts cannot provide a guaranteed  
>> way of automatically building universal binaries of all software.  
>> A very few ports provide a +universal variant.
>
> -- 
> Kevin Ballard
> http://kevin.sb.org
> eridius at macports.org
> http://www.tildesoft.com
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users