On Sat, Jan 19, 2013 at 03:07:50PM +0100, Jon Severinsson wrote:
> On the other hand, debian testing (KDE 4.8 etc.) still shows 36 packages
> still requiring it, so that deprecation notice has obviously not been taken
> all too seriously.
>From looking at the list, it doesn't seem like any of them
On Sunday 20 January 2013 08:02:04 Jeremy Whiting wrote:
> Just to clarify. that page about building qt5 builds the stable branch, and
> in order to change to the dev branch we need to in each submodule do git
> checkout -b dev origin/dev ? or is there some easy way to get all
> submodules on the d
Hello,
On Saturday 19 January 2013 13:36:37 David Faure wrote:
> It's time to drop the Qt4 compatibility, in order to use the new things from
> Qt 5 which we need to continue simplifying dependencies between frameworks.
Also note that I fixed ktcpsockettest this morning to be reliable. It should
lördagen den 19 januari 2013 22:02:11 skrev David Faure:
> On Saturday 19 January 2013 15:07:50 Jon Severinsson wrote:
> > A follow up question: What should we do with kde3support?
> >
> > In it's current form it won't build on Qt5, as it depends on the
> > Qt3Support module that was removed in Q
söndagen den 20 januari 2013 16:02:04 skrev Jeremy Whiting:
> or is there some easy way to get all submodules on the dev branch to build
> the dev version of all of qt5?
If you are starting from scratch, just pass " --branch dev" to git checkout.
Wiki is updated.
To re-use an existing qt5.git c
Just to clarify. that page about building qt5 builds the stable branch, and
in order to change to the dev branch we need to in each submodule do git
checkout -b dev origin/dev ? or is there some easy way to get all
submodules on the dev branch to build the dev version of all of qt5? I
didn't find
On Saturday 19 January 2013 15:07:50 Jon Severinsson wrote:
> lördagen den 19 januari 2013 13:36:37 skrev David Faure:
> > Dear KDE Frameworks hackers,
> >
> > It's time to drop the Qt4 compatibility, in order to use the new things
> > from Qt 5 which we need to continue simplifying dependencies
David Faure wrote:
> On Saturday 19 January 2013 19:07:39 Stephen Kelly wrote:
>> David Faure wrote:
>> > Stephen, you mentionned a script to get rid of the ifdefs for Qt4/Qt5,
>> > do you have that at hand, or does it need to be written?
>>
>> It needed to be adapted from another script that I h
On Saturday 19 January 2013 14:59:54 Alexander Neundorf wrote:
> On Saturday 19 January 2013, David Faure wrote:
> > Dear KDE Frameworks hackers,
> >
> > It's time to drop the Qt4 compatibility, in order to use the new things
> > from Qt 5 which we need to continue simplifying dependencies between
On Saturday 19 January 2013 19:07:39 Stephen Kelly wrote:
> David Faure wrote:
> > Stephen, you mentionned a script to get rid of the ifdefs for Qt4/Qt5, do
> > you have that at hand, or does it need to be written?
>
> It needed to be adapted from another script that I have. Actually I needed
> tw
David Faure wrote:
> Stephen, you mentionned a script to get rid of the ifdefs for Qt4/Qt5, do
> you have that at hand, or does it need to be written?
It needed to be adapted from another script that I have. Actually I needed
two scripts - one to handle #if < 5.0.0, and another for #if >= 5.0.0.
lördagen den 19 januari 2013 13:36:37 skrev David Faure:
> Dear KDE Frameworks hackers,
>
> It's time to drop the Qt4 compatibility, in order to use the new things
> from Qt 5 which we need to continue simplifying dependencies between
> frameworks.
A follow up question: What should we do with kd
On Saturday 19 January 2013, David Faure wrote:
> Dear KDE Frameworks hackers,
>
> It's time to drop the Qt4 compatibility, in order to use the new things
> from Qt 5 which we need to continue simplifying dependencies between
> frameworks.
>
> Please compile Qt5 using the "dev" branch.
Qt 5.0 is
13 matches
Mail list logo
