On 2014-09-22, at 06:33 AM, Adam Strzelecki <o...@java.pl> wrote: >> qmake - framework bundle hierarchy (QTBUG-32895): >> https://codereview.qt-project.org/95454 >> qmake - “_debug" in CFBundleExecutable (QTBUG-32894): >> https://codereview.qt-project.org/95455 >> qmake - add CFBundleVersion: https://codereview.qt-project.org/95456 >> macdeployqt - “Current” version symlinks: >> https://codereview.qt-project.org/#/c/95442/ >> >> Are these patches sufficient? If not, what’s missing? > > Almost. > > The only problem not addressed yet is .prl (i.e. QtCore.framework/QtCore.prl) > file inside the bundle root. It has to be either moved one level up or into > Resources/. Otherwise codesign won't work on built frameworks. > > Of course I am aware that macdepoyqt (probably) strips out this file, but if > someone has some kind of custom deployment step then .prl file may cause > trouble for him as codesign just bails out with "unsealed contents present in > the root directory of an embedded framework" without exactly telling what's > going on.
Good catch. Simple answer: is there ANY reason at all to deploy .prl files? If so, place them in Resources. If not, don't put them anywhere in the framework bundles (instead, $QT_INSTALL_LIBS/lib). > --Adam > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Jake Petroules - jake.petroules at petroules.com Chief Technology Officer - Petroules Corporation _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
