why you need to build Qt? what about using the sdk. I too had many problems with qt builds on mac, finally using sdk for all.
why you need to build Qt? what about using the sdk. I too had many problems with qt builds on mac, finally using sdk for all.
Because it's the only way to support multiple versions of Qt on the Mac.
It built fine, it installs fine, it's in the right place, and a demo project can link to it just fine.
The problem is with this more complex project that brings in a lot of external libs.
I think it's the internal refs in the external dylibs that is causing the problem - I have to go through them all and see what's up with those, I guess.
Voila! It is the embedded rpaths in the external dylibs and frameworks.
I wrote a python tool to straighten those out so they're self-consistent and point to the correct dependencies, and the '<library> not found' error went away.
Now, I only have a small problem with Xerces.... (ptui...)
Bookmarks