Universal Binaries

[Altoine Barker]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I know what company you speak of and they will continue to remain
nameless, but all they had to do was change the default directory of
their program. I found that to be quite amusing myself but a good lesson
learned. Well, it was the default directory and it seemed that it was
hard for them to figure out how to get it to run with as little of fink
libraries as possible. LoL Easy if you code from scratch, but not if you
have experience using package and porting programs.

- -Altoine


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 <mailto:eridius at macports.org>
>> http://www.tildesoft.com
>>
>>
>> _______________________________________________
>> macports-users mailing list
>> macports-users at lists.macosforge.org
>> <mailto:macports-users at lists.macosforge.org>
>> http://lists.macosforge.org/mailman/listinfo/macports-users
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF3ziaS0foIafBdlkRAguYAJ0aJie6kRWuAVsMdPsaybpUg89g+QCfcLaE
9jJsDuZeRlX3kVaLMKKFN28=
=NREz
-----END PGP SIGNATURE-----