Re: [Development] Co-installation & executable naming rules

2012-10-09 Thread Ziller Eike
On 8 Oct 2012, at 14:58, Simon Hausmann wrote: > On Friday, September 21, 2012 05:24:16 PM Thiago Macieira wrote: >> On sexta-feira, 21 de setembro de 2012 16.47.11, Thiago Macieira wrote: >>> Include the major version number (5) in all library base names, like on >>> Windows, on all platforms.

Re: [Development] Co-installation & executable naming rules

2012-10-09 Thread Lincoln Ramsay
On 9/10/12 5:17 PM, Simon Hausmann wrote: > On Tuesday, October 09, 2012 09:07:10 AM Lincoln Ramsay wrote: >> On 08/10/12 22:58, Simon Hausmann wrote: >>> Now this has some ugly implications, everyone will have to change the way >>> they develop with Qt 5. In this context we have another interestin

Re: [Development] Co-installation & executable naming rules

2012-10-09 Thread Simon Hausmann
On Tuesday, October 09, 2012 09:07:10 AM Lincoln Ramsay wrote: > On 08/10/12 22:58, Simon Hausmann wrote: > > Now this has some ugly implications, everyone will have to change the way > > they develop with Qt 5. In this context we have another interesting > > artifact: People who have been developi

Re: [Development] Co-installation & executable naming rules

2012-10-08 Thread Lincoln Ramsay
On 08/10/12 22:58, Simon Hausmann wrote: > Now this has some ugly implications, everyone will have to change the way they > develop with Qt 5. In this context we have another interesting artifact: > People who have been developing Qt for a long time as part of company efforts > such as Trolltech, N

Re: [Development] Co-installation & executable naming rules

2012-10-08 Thread Simon Hausmann
On Monday, October 08, 2012 02:31:46 PM shane.kea...@accenture.com wrote: [...] > Another thing you need to consider is named versions. > For example I might have "5.0.0" and "5.0.0-blackberry" co-installed. > I think Qt Creator handles this just fine, but the "qt --5" examples above > look like it

Re: [Development] Co-installation & executable naming rules

2012-10-08 Thread shane.kearns
> We just had a discussion in the Oslo office about this. We suggest to > basically follow your proposal, with an addon to hide some of the > uglyness it brings along. > > Let me try to summarize very shortly. The base proposal would be to > include the major Qt version throughout the project: > >

Re: [Development] Co-installation & executable naming rules

2012-10-08 Thread Simon Hausmann
On Friday, September 21, 2012 05:24:16 PM Thiago Macieira wrote: > On sexta-feira, 21 de setembro de 2012 16.47.11, Thiago Macieira wrote: > > Include the major version number (5) in all library base names, like on > > Windows, on all platforms. On Windows we already have QtCore5.dll and > > QtV85.

Re: [Development] Co-installation & executable naming rules

2012-09-24 Thread Ziller Eike
On 24 Sep 2012, at 11:30, Thiago Macieira wrote: > On segunda-feira, 24 de setembro de 2012 09.14.27, Ziller Eike wrote: >>> Let me ask you a question, though: suppose someone installs Qt 5 globally >>> as frameworks (/System/Frameworks/QtCore.framework), then updates Qt 4.8. >>> Which is the de

Re: [Development] Co-installation & executable naming rules

2012-09-24 Thread Thiago Macieira
On segunda-feira, 24 de setembro de 2012 09.14.27, Ziller Eike wrote: > > Let me ask you a question, though: suppose someone installs Qt 5 globally > > as frameworks (/System/Frameworks/QtCore.framework), then updates Qt 4.8. > > Which is the default symlink target? > > There is no "default symlink

Re: [Development] Co-installation & executable naming rules

2012-09-24 Thread Ziller Eike
On 24 Sep 2012, at 09:49, Thiago Macieira wrote: > On segunda-feira, 24 de setembro de 2012 07.19.30, Ziller Eike wrote: >> I don't think the recommendation applies to Mac. >> >> Usually you won't have globally installed Qt. Most applications deploy their >> used libraries within the applicatio

Re: [Development] Co-installation & executable naming rules

2012-09-24 Thread Thiago Macieira
On segunda-feira, 24 de setembro de 2012 07.19.30, Ziller Eike wrote: > I don't think the recommendation applies to Mac. > > Usually you won't have globally installed Qt. Most applications deploy their > used libraries within the application's app bundle (that's what we have > macdeployqt for). Eve

Re: [Development] Co-installation & executable naming rules

2012-09-24 Thread Ziller Eike
On 21 Sep 2012, at 17:24, Thiago Macieira wrote: > On sexta-feira, 21 de setembro de 2012 16.47.11, Thiago Macieira wrote: >> Include the major version number (5) in all library base names, like on >> Windows, on all platforms. On Windows we already have QtCore5.dll and >> QtV85.dll, so I reco

Re: [Development] Co-installation & executable naming rules

2012-09-21 Thread Thiago Macieira
On sexta-feira, 21 de setembro de 2012 17.24.16, Thiago Macieira wrote: > Good examples are: qtcreator, assistant, linguist, qmlviewer, qmlscene, > qmlplugindump, qmlprofiler, xmlpatterns, qdbus, qdbusviewer, qglinfo Actually, the qml ones are not good examples since they can load plugins.

[Development] Co-installation & executable naming rules

2012-09-21 Thread Thiago Macieira
On sexta-feira, 21 de setembro de 2012 16.47.11, Thiago Macieira wrote: > Include the major version number (5) in all library base names, like on > Windows, on all platforms. On Windows we already have QtCore5.dll and > QtV85.dll, so I recommend having libQtCore5.so.5. For Mac, I'm not sure of > th