falcon and rev-upgrade

[Jeremy Lavergne]

> Yes, unfortunately they need the change, too, although not using -id but
> using some other parameter of install_name_tool. If you could find a way
> to change the id of the library before all the other stuff gets linked
> against it, that would certainly simplify your life a lot.
> I guess libtool has a way to make sure the correct id gets written into
> the library while building, but I don't know for sure about this one;
> you might want to ask on -devel how to do this correctly.

Clemens: Cool, thanks.

Devs: So the story goes, falcon has a library that named itself with a relative path. This was then sucked into all the subsequent falcon libraries. I'm able to correct it using `install_name_tool -id`, and I aim to do the same for the rest using of the libraries and binaries using `install_name_tool -change`. Is this correct?

Also, it might become handy to create a portgroup for running install_name_tool, as you can make a list of tuples comprised of the correct ID and what files need it replaced. The portgroup could pull the old id value from the actual library so it can easily do -change for subsequent files.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 8796 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20120123/9cdd5981/attachment-0001.bin>