Hi Ryan, Kevin, On 25 Jun 2007, at 06:48, Ryan Schmidt wrote:
On Jun 24, 2007, at 08:57, source_changes@macosforge.org wrote:
Revision: 26461 http://trac.macosforge.org/projects/macports/changeset/ 26461 Author: pipping@macports.org Date: 2007-06-24 06:57:23 -0700 (Sun, 24 Jun 2007)
Log Message: ----------- initial upload of <merge.rb>
merge.rb is designed to merge two or more trees of single-arch destdirs into a single destdir of universal binaries.
Now, what it is this? You may recall I mentioned the "unify" script on the mailing list some time ago, which based on your description, does what your merge.rb script does. Why reinventing the wheel?
http://lists.macosforge.org/pipermail/macports-dev/2007-March/ 000864.html
http://lists.macosforge.org/pipermail/macports-dev/2007-April/ 001319.html
Do you have any further information on unify.pl? Does it have a web page or some documentation? I wasn't aware of it neither and also missed your previous mails. I do not expect though, that we are reinventing the wheel: The requirements that I'd expect Mozilla to have on such a tool differ quite a bunch to ours: Mozilla knows what they are building and they know that both builds are "the same" stuff - we don't (e. g. some software may enable features on certain archs). We also do not only need to merge two binaries, we also need to test and merge different kind of files, like C header files, pkgconfig files, libraries, etc. I'd expect the actual lipo-ing of binaries to be the smallest part on Elias' tool - if that's what unify.pl is doing, I see no problems. I'd be happy for more information on unify.pl - searching the net I don't find anything. :/ Regards, -Markus --- Markus W. Weissmann http://www.mweissmann.de/