Problem deploying statically linked Qt for macOS
-
When making Qt statically linked this happens...
-
Hi,
What exact parameters did you pass to configure ?
On a side note, don't forget the licensing implication of using a static build of Qt.
-
I've followed this, put no parameters in "<other parameters>"
-
What version of Xcode are you using ?
-
I also find something suspicious with my paths, they don't look to match exactly the paths describe the ones in the guide, check the first pwd command and the location of the configure files
-
First thing to do: do an out of source build. That should avoid you some trouble.
You installed Qt in the /Application folder which is likely write protected in some aspects.
-
thank you for the answer, I'll do that but I thought it caused no trouble, meanwhile I discovered that there is a macdeployqt, something I've missed and solved my problem, either way what you're saying about the location of my Qt installation might have caused me already some strange behaviors sometimes, I'll reinstall once I have the time. Do you think i's better to use macdeployqt than statically linked qt?
-
Yes it does. For several reasons:
- you don't face the same licensing constraints as with the use of a static build of Qt.
- Apple's guidelines is in the favour of using frameworks rather than static libraries which is something to take into account if you plan to distribute your application through the Mac App Store
- A static build is pretty long and heavy to do
