macdeployqt is broken due to change in plugin extension

[lord@…]

In q4-mac-4.5.2 port there is a mention that it changes plugin extension to .bundle from .dylib used in original QT.

They are indeed bundles but for portability reasons QT uses for them shared lib extension, which is .dylib on mac. So it does not copy plugins into app bundles making the non-portable.

The change breaks qtmacdeploy utility which searches plugins using .dylib extension.

[morten.sorvig@…]

Replying to macsforever2000@…: I could modify macdeployqt to handle .bundle as well, if there are good reasons for keeping the .dylib -> .bundle rename in MacPorts

[lord@…]

Replying to morten.sorvig@…:

Replying to macsforever2000@…: I could modify macdeployqt to handle .bundle as well, if there are good reasons for keeping the .dylib -> .bundle rename in MacPorts

Trolltech might had their reasons to do so. I think what you trying to do is not part of a port but part of QT improvement. If you do want plugins on mac to be called .bundle you better submit patch to QT, so they change it in the main source.

[sharky@…]

Does anyone have any idea why we rename the plugins extension at all in macports? What are the benefits?

[sharky@…]

Cc Me!

[michaelld (Michael Dickens)]

Is this issue still relevant as of r72571 with qt4-mac being at 4.7.0?

[michaelld (Michael Dickens)]

Qt 4.7.0 as installed by MacPorts uses .dylib for all libraries and plugins. Hence I'm closing this ticket as fixed; please reopen if it is not fixed for you.