On Fri, 17 Sep 2010 14:34:44 +1000, Max Matveev wrote:
makc> On Fri, 17 Sep 2010 14:19:31 +1000 (EST), Nathan Scott wrote:
nathans> (IOW, where the Qt frameworks we link with are shipped with
nathans> the PCP GUI package, such that no separate Qt installation
nathans> needed on users machine?)
makc> I don't think there would be - my experience with troll's is that if
makc> you let them control the build then they make sure it works most of
makc> the time.
makc> Personally I don't like private frameworks for apps on Mac OS - if
makc> done without too much thinking it just adds to bloat: consider what
makc> would happen if private frameworks ship with pcp-gui - 4 .app
makc> bundles, 4 copies of Qt?
After a bit of experimentation I can see two and a bit options:
1. use macdeployqt to copy Qt bits into pmchart.app, pmtime.app,
pmdumptext.app and pmquery.app, modify install rules to populate
install tree with individual copies of Qt bits for each .app.
Result: each .app comes with its own life support system
1.1 as above but only do it for pmchart.app, the others are modified
via install_name_tool to point to pmchart's copy of Qt bits - saves
some space but creates a dependency on pmchart.app: if it moves
then other applications will stop working.
2. Ship all Qt bits in /Library/PCP/Frameworks (should it be
/Library/Application Support/PCP?) and use install_name_tool to
change all binaries to use Qt from /Library/PCP/Frameworks.
My preference would be for #2. I may even have a mac box which does
not have Qt installed yet to test this scenario.
nathans> If that can be made to work, lets switch for 1.5.0 ... ?
makc> I'll play a bit with this.
It mostly works, I just need to smooth some rough edges (like
installing Qt bits too many times).
max
|