Re: Best practice for libraries supporting both Qt4 and Qt5

2013-12-12 Thread David Faure
On Sunday 01 December 2013 14:18:35 Thiago Macieira wrote: > On domingo, 1 de dezembro de 2013 13:42:15, Rex Dieter wrote: > > Allan Sandfeld Jensen wrote: > > > On Thursday 28 November 2013, Michael Palimaka wrote: > > >> Any thoughts? > > > > > > In an ideal world we would convince the distros t

Re: Best practice for libraries supporting both Qt4 and Qt5

2013-12-01 Thread Thiago Macieira
On domingo, 1 de dezembro de 2013 13:42:15, Rex Dieter wrote: > Allan Sandfeld Jensen wrote: > > On Thursday 28 November 2013, Michael Palimaka wrote: > >> Any thoughts? > > > > In an ideal world we would convince the distros to enable Qt namespace on > > Qt5, so that Qt4 and Qt5 symbols does not

Re: Best practice for libraries supporting both Qt4 and Qt5

2013-12-01 Thread Rex Dieter
Allan Sandfeld Jensen wrote: > > On Thursday 28 November 2013, Michael Palimaka wrote: >> >> Any thoughts? >> > In an ideal world we would convince the distros to enable Qt namespace on > Qt5, so that Qt4 and Qt5 symbols does not clash, and does not cause > crashes when loaded as plugins etc.

Re: Best practice for libraries supporting both Qt4 and Qt5

2013-12-01 Thread Allan Sandfeld Jensen
On Thursday 28 November 2013, Michael Palimaka wrote: > > Any thoughts? > In an ideal world we would convince the distros to enable Qt namespace on Qt5, so that Qt4 and Qt5 symbols does not clash, and does not cause crashes when loaded as plugins etc. `Allan

Best practice for libraries supporting both Qt4 and Qt5

2013-11-29 Thread Michael Palimaka
Hi, Is there an established best practice for libraries to support both Qt4 and Qt5? Currently, some libraries such as phonon rename their Qt5 versions, permitting full parallel installation and usage (even of development and CMake config files). Other libraries such as attica bump the maj