Opened 14 years ago

Closed 12 years ago

#27959 closed defect (fixed)

qt4-mac: macdeployqt doesn't copy qt_menu.nib in the application bundle

Reported by: farangfrog Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc:
Port: qt4-mac

Description

After invoking macdeployqt on an application using qt4-mac, the application fails with the error "qt_menu.nib could not be loaded". Inspection of the bundle shows indeed that qt_menu.nib is not at its expected location "Content/Resources".

Manually copying qt_menu.nib from /opt/local/lib/Resources inside the bundle resolves the issue.

Change History (11)

comment:1 Changed 14 years ago by mf2k (Frank Schima)

Owner: changed from macports-tickets@… to michaelld@…
Summary: macdeployqt doesn't copy qt_menu.nib in the application bundleqt4-mac: macdeployqt doesn't copy qt_menu.nib in the application bundle

comment:2 Changed 14 years ago by michaelld (Michael Dickens)

Hmm ... I haven't looked at the code yet, but I'll bet that this would be easily fixed is qt4-mac were installed as a framework instead of separate libraries & such. qt4 when installed not as framework doesn't install the Resources directory -- I had to add that. YA reason to think of switching to just framework (beyond ticket #27558: making use of the way framework libraries are linked so-as to allow for easier debugging). Do you have any objection to going framwork? Most end-users just want Qt to work, and otherwise don't care how it is installed.

comment:3 Changed 14 years ago by farangfrog

Yes, that makes sense. No objection to going framework..

comment:4 Changed 13 years ago by michaelld (Michael Dickens)

I'm looking at this issue (finally), since there's another issue with macdeployqt to be fixed. From what I understand, if you install "qt4-mac +framework", then macdeployqt works as expected. But, because qt4-mac's default is to not install as framework, then we get this issue. I use Qt via Python only thus far, so I haven't made use of macdeployqt. Can you attach an simple archive, and/or directions, with a very simple example of how to use macdeployqt so that I can do some sleuthing & try to work this issue out?

comment:5 Changed 12 years ago by michaelld (Michael Dickens)

There's a new qt4-mac in place now; I don't know if it will help with this issue, but please do a "port selfupdate" and then "upgrade outdated" and then see if this ticket is still valid.

comment:6 Changed 12 years ago by devernay (Frédéric Devernay)

I confirm the bug is still present in qt4-mac@4.8.2_0

for your information, macdeployqt is also broken in the +Framework version (it thinks the frameworks are in /opt/local/Library/lib instead of /opt/local/Library/Frameworks)

comment:7 Changed 12 years ago by michaelld (Michael Dickens)

OK; thanks for the info. I'll look into it as time allows. Seems like this is a bigger issue now if it doesn't work with either variant (library or framework). Thanks for getting back!

comment:8 Changed 12 years ago by devernay (Frédéric Devernay)

I just made a ticket #35067 for a fix to the +framework variant

comment:9 Changed 12 years ago by michaelld (Michael Dickens)

OK; thanks.

comment:10 in reply to:  8 Changed 12 years ago by michaelld (Michael Dickens)

Replying to frederic.devernay@…:

I just made a ticket #35067 for a fix to the +framework variant

So, with this fix installed, does it fix this ticket's issue as well?

comment:11 Changed 12 years ago by michaelld (Michael Dickens)

Resolution: fixed
Status: newclosed

Fixed in r97950.

Note: See TracTickets for help on using tickets.