Ticket #35067 (closed defect: fixed)
qt4-mac: macdeployqt thinks frameworks are in a wrong location (+framework variant)
| Reported by: | frederic.devernay@… | Owned by: | michaelld@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.1 |
| Keywords: | haspatch | Cc: | |
| Port: | qt4-mac |
Description
macdeployqt thinks the frameworks are in prefix/Library/lib, whereas they are in prefix/Library/Frameworks. The consequence is that it doesn't change the framework location in the binary, and the app is not standalone.
The fix is very simple (patch attached)
Attachments
Change History
Changed 11 months ago by frederic.devernay@…
- Attachment patch-tools_macdeployqt_shared_shared.cpp.diff added
comment:1 Changed 11 months ago by ryandesign@…
- Owner changed from macports-tickets@… to michaelld@…
- Keywords haspatch added
comment:2 Changed 11 months ago by michaelld@…
Hmm ... I wonder if there's a way to distinguish between a LIBRARY path and FRAMEWORK path, such as what I set up with the new qt4-mac? I'd much prefer to be able to switch between them depending on how Qt is installed, rather than hard-coding the search path depending on how Qt is installed. I'll take a look at the code that you patched to see what's up with it.
comment:3 Changed 11 months ago by frederic.devernay@…
the single line affected by the patch actually only affects Qt libraries that appear in the "otool -L ..." output as "*.framework", whereas libraries installed by the non-framework version appear as "*.dylib", so the patch shouldn't break the non-framework version

