On 2014-08-04, at 08:22 AM, Thiago Macieira <[email protected]> wrote:
> On Monday 04 August 2014 12:22:01 Adam Strzelecki wrote: >> I have wrote that your suggestions should be implemented without any doubt, >> but whether copy on build should be default it is really a matter of >> preference, that's why this has to be config option which may be default or >> not, I don't care, I don't want to argue about that. All I care it to have >> a choice. > > Let's put it this way: > > - qmake should not generate code that copies on make > - macdeployqt should do that copying > > Qt Creator can choose between running macdeployqt or setting DYLD_xxx_PATH. > My > suggestion is to run macdeployqt for bundle applications since they may be > attempting to use resources inside their bundles. Generally, I agree, but I prefer Ossi's solution where *deployqt is a qmake backend rather than a public tool. Keep in mind that there is really nothing Qt-specific about macdeployqt functionality. windeployqt, maybe, macdeployqt, no. For most real world projects, there are non-Qt libraries that need to be copied to the bundle as well, and this is the job of the build system - no user should ever manually touch macdeployqt. It is a mere implementation detail. > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development -- Jake Petroules - jake.petroules at petroules.com Chief Technology Officer - Petroules Corporation _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
