qt4-mac and macdeployqt

[Michael Dickens]

On Feb 2, 2011, at 11:36 AM, Petr Vanek wrote:
> it looks like the macdeployqt is broken in qt4-mac (since the port use dylibs instead of frameworks)

Hi Petr - I think this issue is ticket #27959, btw.  This issue is probably somewhere between MacPorts and Qt, but more towards the latter than the former.  By default, Qt builds as a framework on Darwin / OSX, but one can disable this behavior via a configure flag (which is what qt4-mac 4.7.1 does).  When installed as "-no-framework", the "resources" are not installed by Qt during "make install" -- I figured that out the hard way, and just copy them over during post-destroot.  My bet is that "macdeployqt" does a basic check for "framework or not", and if the latter then doesn't install the resources either -- no matter that it is creating the .app on OSX-style.  So, by moving to +framework in MacPorts, I bet we resolve this issue without having to hack into "macdeployqt"s source code or QMake files or whatever.  That's my "proposed" solution right now, which I will implement once Qt 4.7.2 comes out.  Hope this helps! - MLD