Universal Binaries

Julian Yu-Chung Chen julian9 at gmail.com
Fri Feb 23 12:29:01 PST 2007

I agree it is a good practice to build my own copy of required  
libraries. I know how troublesome it is finding that some
application is dependent on things installed in /sw. Pity to the  
nameless company. ;-)

In my case I don't really bundle MacPorts library files in my app nor  
require them in place during runtime.
I just need them to build my library and having universal binary out  
of box is handy.

On Feb 23, 2007, at 11:43 AM, Jordan K. Hubbard wrote:

> There is a corollary to this, which is even if you do bundle up the  
> appropriate MacPorts bits, you're now polluting a namespace that's  
> not really under your control.  A commercial company who shall  
> remain nameless found this out to their displeasure when they  
> shipped software which installed (and relied upon) something in /sw/ 
> lib/... (they used Fink, obviously).   Unfortunately, the version  
> they shipped in /sw had been customized in some way (if memory  
> serves me correctly) and many Fink installations ended up  
> installing their own version over it and blowing the commercial  
> software up without even knowing why.   The commercial company had  
> to ship an update which removed the dependency and I don't know how  
> much that cost them in terms of engineering time and dollars, but  
> I'm sure they regretted doing it in the first place.
> - Joradn
> On Feb 23, 2007, at 9:26 AM, Kevin Ballard wrote:
>> 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
>> 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

More information about the macports-users mailing list