How to fix path in third-party libs which usage another third-party libs after macdeployqt?

[shav]

Ok, I will try to find another way how to fix the path for customer.

[SGaist]

Hi,

You should run ma deploy Qt with the verbose option on to see what is happening with these external libraries.

If it’s only this one you can copy it by hand and run install_name_tool on it.

[florent_lightingsoft]

Hello
i have actually same problem with same Library :

Dyld Error Message:
  Library not loaded: /usr/local/Cellar/nettle/3.3/lib/libnettle.6.dylib
  Referenced from: /private/var/folders/8h/6gwsfzvd0497x5v7dqkf6dg80000gp/T/AppTranslocation/AC4CC981-7245-4236-9929-4EF95D0225B1/d/StoreUpgradeTools.app/Contents/Frameworks/libhogweed.4.dylib
  Reason: image not found

Did you fixe it ?

[shav]

@florent_lightingsoft
Yes, but you need to do this for every lib which generate this error.

install_name_tool -change "old_path" "@executable_path/../Frameworks/lib_name" lib_path_for_update
install_name_tool -change "old_path" "@executable_path/../Frameworks/lib_name" app_binnary_path_for_update

If you find a way to use this commands for all lib and sub-libs by script let me know, because for now I use this for every lib manually.

[ngn999]

@shav said in How to fix path in third-party libs which usage another third-party libs after macdeployqt?:

@florent_lightingsoft
Yes, but you need to do this for every lib which generate this error.

install_name_tool -change "old_path" "@executable_path/../Frameworks/lib_name" lib_path_for_update
install_name_tool -change "old_path" "@executable_path/../Frameworks/lib_name" app_binnary_path_for_update

If you find a way to use this commands for all lib and sub-libs by script let me know, because for now I use this for every lib manually.

it's 2022, same problem here. any solution?

[ngn999]

I'm sure it's about this bug:
https://bugreports.qt.io/browse/QTBUG-56814

but the fix is not complete, it can't deal with some libraries , such as ffmpeg and nettle.

I made a bugfix here: https://github.com/ngn999/qttools/commit/5be4d44508c3a8b4d739de30929d9158b84b4e50

based on 6.2.4.

[SGaist]

@ngn999 hi and welcome to devnet,

Would you make a submission to the official repo so it can be integrated for all ? :-)

[ngn999]

@SGaist yes, I submit a pull request to 6.2.4 https://github.com/qt/qttools/pull/5

[SGaist]

GitHub is just a mirror. Here you can find the procedure to get you started. Don't worry about the size of the page, it's just very detailed instructions :-)

[ngn999]

@SGaist OK. I'll look at it.

[ngn999]

@SGaist I have submitted one code review: https://codereview.qt-project.org/c/qt/qtbase/+/405490

by the way, the workflow is complex.

[SGaist]

Thanks !

I also found it the first time but it quickly becomes easier.

You forgot to add reviewers. Usually the best is to check the persons that reviewed the submissions applied to the file you changed.