#36431: qt4-mac: macdeployqt shows errors when trying to copy in frameworks -------------------------+------------------------- Reporter: mavaugha@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: qt4-mac | -------------------------+------------------------- Comment (by michaelld@…): Can you use "qwt-devel" instead of "qwt-60"? I updated the former recently to version 6.0.1 without realizing that the latter existed :) That's what I have installed right now, and it seems to work well for me. I haven't tried it with macdeployqt yet; I think I can tell if that plugin is being used, but I don't know of a .app that uses it specifically -- so, you're probably in a better space to test it out to see if that's really one of the issues. I'm guessing that the issue with where the plugins are located has to do with the way macdeployqt finds and copies the necessary frameworks; probably the second time, since nothing was copied, the "pluginpath" comes up empty and hence the default is used (the /opt/local/share/qt4/ value). The first time, I'm guessing that the "pluginpath" comes up as "/opt/local" ... but that's just guessing. This is pretty simple to test if you install qt4-mac with "-k" as an option to keep the build directory; then you can edit the macdeployqt, build it, and test out the resulting executable without reinstalling it -- this is what I've been doing to see how macdeployqt works internally. -- Ticket URL: <https://trac.macports.org/ticket/36431#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS