2014-05-11 14:15 GMT+02:00 PCMan <pcman...@gmail.com>:
> On Sun, May 11, 2014 at 8:08 PM, Julien Lavergne <gi...@ubuntu.com> wrote:
> >
> >
> >
> > 2014-05-09 15:30 GMT+02:00 Jerome Leclanche <adys...@gmail.com>:
> >
> >> > 2014-05-09 11:53 GMT+02:00 Jerome Leclanche <adys...@gmail.com>:
> >> >
> >> >> The second point is about Qt 5. There's been spiking interest in
> >> >> finishing the port and we're actually almost there. As soon as the
> >> >> desktop fully compiles with Qt 5 I will switch the Arch packages to
> >> >> use that everywhere. I believe that this is something we need to
> >> >> finish first before anything can happen on the graphics side, as Qt 5
> >> >> has a very different set of widget themes.[1]
> >> >
> >> >
> >> > I think this should be the priority. I'm preparing the schedule for
> the
> >> > next
> >> > releases of Lubuntu, and I'm quite uncomfortable to tell people that
> we
> >> > are
> >> > going to break the system twice : one for the migration to Qt, and one
> >> > for
> >> > the migration to Qt5. I'll prefer to break everything just once :-)
> >>
> >> That's a good point and I agree.
> >>
> >> J. Leclanche
> >>
> >> >
> >> > I tried to compile liblxqt yesterday with the qt5 branch, but even
> with
> >> > a
> >> > couple of adjustments, it didn't want to compile, and my poor C++ / Qt
> >> > skills blocked my work :-/ Any documentation for Qt4 => Qt5 migration
> is
> >> > welcome :-)
> >
> >
> > Well, I spend some time this week-end, and I think it's working now. See
> :
> > https://github.com/gilir/liblxqt-qt5
> >
> > I started from the qt5 branch, I tried to adjust it in the same spirit
> > (since there is more than a qt5 on this branch). Any comments are very
> > welcome.
> Nice work!
> BTW, Luis seems to have some cmake scripts for handling qt4/qt5, will
> it be better if we integrate his work?
> The name of the library and the headers are changed a bit when USE_QT5
> is enabled.
> This will introduce problems for other components.
>
Yes, if it's merged like this, it breaks all the lxqt components, even if
compiled with qt4. I'm not sure if it's purpose of the work in progress in
the original qt5 branch, so I let it as it.
>
> > I also ported lxqt-about, just to see if it's working properly :
> > https://github.com/gilir/lxqt-about-qt5
>
> Looks OK, but will it be better if we can use portable header names
> instead of lots of #ifdef and <lxqt5/xxx.h>?
>
That would be nice to be able to build 2 versions of liblxqt with Qt4 and
Qt5, but in this case, 2 headers will be installed and should note
conflict. If there is an easier way, I'm open to comments :-) Or, if we are
able to migrate all the components to Qt5 at once, it will be not necessary
:-)
Regards,
Julien Lavergne
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
