Solved macdeployqt and poppler
-
I have been using macdeployqt fro some time to generate portabel osx apps.
We are using poppler which is installed in /usr/local/bin.
macdeployqt does not find the library unless there is a link in /usr/lib to it.
Unfornately osx inhibits setting links there in newer versions of osx, so how do I tell macdeployqt where to find the library ?
DYLD_FALLBACK_LIBRARY_PATH is ignored, setting DYLD_LIBRRAY_PATH break functionaliyt completely... -
Hi,
Which version of Qt are you using ?
-
I am using qt 5.7
-
How did you install poppler ?
-
Self-compiled via cmake/make/make install to /usr/local/lib.
-
What if you add
-libpath=/usr/local/lib
to your macdeployqt call ? -
macdeployqt does not know the option -libpath or any other option which influence the lib search order.
-
Then check that you are calling macdeployqt from your Qt 5.7 installation.
macdeployqt -h
shows you all the options from the application. -
@jsundermeyer macdeployqt has always been pretty weak. In every commercial application I've written for osx I've had to write some sort of bash script in order to make a deployable application. I gave up on macdeployqt long ago for exactly these types of issues.
You can just make a bash script that does what you need it to and it can find the correct libs for you. ;)
-
I was hoping since macdeployqt nearly manages to do it right, it might be tweaked a bit, before starting doing everything with a script of my own.
-
@SGaist neither qt documentation nor macdeployqt -h give any hints on how to give library search paths. Mind you, I have been using it for years.
-
indeed macdeployqt abc.app -libpath=/usr/local/lib works.
The issue was that the new option was introduced in qt 5.7.1 and I was still using 5.7.0.