Ticket #2927 - Mac application bundler doesn't track library versions

This subforum is specifically to discuss packaging issues on different platforms (windows, mac, linux), and using different packaging systems (conda, etc...)
User avatar
Kunda1
Posts: 5818
Joined: Thu Jan 05, 2017 9:03 pm

Ticket #2927 - Mac application bundler doesn't track library versions

Postby Kunda1 » Thu Sep 05, 2019 9:41 pm

Discussion thread for issue #2927 - Mac application bundler doesn't track library versions
I've run in to an issue on my own machine, where the linker finds a newer version of a library than the one that ends up getting copied in to the application bundle. This causes the older library to not be loaded by dyld when the bundle is launched, which can cause a range of problems.

There are several (and, to me at least, some are non-obvious) places in the existing script that need to take library versions in to account. After mucking around with it script for a few hours to find the source of my problem, I'm thinking that it'll be best to re-write the part that creates the graph of dependencies.

(note to self: Local branch is 20170225-bundle-tool)
Other changes:
* dir_filter in main() needs to be more Python version-agnostic
* before calling otool, etc on libraries mentioned, the script should ensure that the library actually exists, and respond accordingly.
Want to contribute back to FC? Checkout:
#lowhangingfruit | Use the Source, Luke. | How to Help FreeCAD | How to report FC bugs and features
chrisb
Posts: 19044
Joined: Tue Mar 17, 2015 9:14 am

Re: Ticket #2927 - Mac application bundler doesn't track library versions

Postby chrisb » Thu Sep 05, 2019 10:09 pm

Shouldn't this be in Help or even better Install/Compile forum?