Yes, as a technology preview.
--
Tuukka
> Jeff Tranter kirjoitti 21.12.2015 kello 19.38:
>
> I was curious if Qt SerialBus is still planned to be in the Qt 5.6.0 release,
> given that it was not included in the beta?
> ___
> Development mailing list
Hi Simon.
The conflict happens in a dozen files in qtbase/src/dbus/ and qttools/src/qdbus.
I just wrote my mail so other can save the time i spend on figuring out what is
wrong with the new qt version.
As I wrote in another mail, for wince bus should be set to no by default, as it
was before ( b
We ran into similar issues in a few places and the established workaround is a
carefully placed #undef interface. Would you be able to tell us where the
conflict happened or maybe even make a patch? (see qtnetwork for a similar
#undef)
Simon
From: Gunnar Roth
Sent: Monday, December 21, 2015 1
Hi Thiago,
> Am 21.12.2015 um 19:46 schrieb Thiago Macieira :
>
> On Monday 21 December 2015 17:44:19 Gunnar Roth wrote:
>> Hi,
>> the problem is that dbus is set to runtime instead of no for windows from
>> configure when no dbus support is found. So it is being tried to build it,
>> which fails,
On Monday 21 December 2015 17:44:19 Gunnar Roth wrote:
> Hi,
> the problem is that dbus is set to runtime instead of no for windows from
> configure when no dbus support is found. So it is being tried to build it,
> which fails, mostly due to using 'interface' as identifier, which seems to
> be a d
I was curious if Qt SerialBus is still planned to be in the Qt 5.6.0
release, given that it was not included in the beta?
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi,
the problem is that dbus is set to runtime instead of no for windows from configure when no dbus support is found. So it is being tried to build it, which fails,
mostly due to using 'interface' as identifier, which seems to be a define somewhere in the wec2013 headers. I wil add -no-dbus to m
Thanks and congrats for Qt 5.6 beta from my side too!
I had the same question has Helio did, about missing .tar.xz. Nothing
urgent, as long as they'll be available at least for the RC and final
releases.
-Timo
2015-12-18 17:32 GMT+02:00 Helio Chissini de Castro :
> Thanks for the work Jani
>
> W
Hi all,
According to current plans we will have Qt 5.7 feature freeze 15th Jan 2016.
That is already quite close so we should have pretty good understanding of new
features for Qt 5.7. So please start listing all new features for Qt 5.7 in new
features list ( https://wiki.qt.io/New_Features_in
Hi,
On Mon, Dec 21, 2015 at 9:48 AM, Jokiniva Jukka
wrote:
> · If you don’t already have Qt credentials, all you need to do is
> register at https://login.qt.io/register* using the same email address you
> currently use for Bug Tracker and Code Review. If you want to change to a
> differe
On Sun, Dec 20, 2015 at 11:15:19AM +0100, Giuseppe D'Angelo wrote:
> Il 20/12/2015 08:56, Frederic Marchal ha scritto:
> >In the meantime, while I'm taming gerrit, how do I inform any reader of
> >QTBUG-50068 that I'm working on a patch?
>
> After you push your patch to gerrit you can simply leave
>>-Original Message-
>>From: Development [mailto:development-boun...@qt-project.org] On Behalf
>>Of Sean Harmer
>>Sent: 21. joulukuuta 2015 11:22
>>To: development@qt-project.org
>>Subject: Re: [Development] Heads up for Qt Bug Report & Code Review users
>>
>>On Monday 21 December 2015 08:4
On Monday 21 December 2015 08:48:37 Jokiniva Jukka wrote:
> Hi,
>
> Some months ago we asked all Qt users to provide us input on ideas to
> further improve the Qt developer experience. You spoke. We listened. It was
> overwhelmingly clear that single sign-on for all Qt Services was at the top
> of
Hi,
Some months ago we asked all Qt users to provide us input on ideas to further
improve the Qt developer experience. You spoke. We listened. It was
overwhelmingly clear that single sign-on for all Qt Services was at the top of
desired features and functionality. Since then, we have been work
14 matches
Mail list logo
