IMO
https://codereview.qt-project.org/#/c/151180/1/qtserialbus.pro
should fix it. Is there a bug report already that I can link to?
Regards
Kai
> -Original Message-
> From: Development [mailto:development-
> bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of
> Thiago Mac
Dear list,
I'm trying to understand a strange situation and hope you can enlighten me.
In December I have raised QTBUG-49971 (a FTBFS bug) since it was not
possible to build MinGW 4.9 with the alpha sources and also from git since
then. The issue is obvious: Commit e19bedc8466a6b8086a0048b7b88c0f6
On quinta-feira, 3 de março de 2016 07:50:51 PST Knoll Lars wrote:
> >It matters because it breaks the build.
> >
> >Please remove it from the build. It's ok for it to be present, but don't
> >compile it.
>
>
> Which build are you talking about? The split source packages shouldn't have
> a probl
On 03/03/16 08:31, "Development on behalf of Thiago Macieira"
wrote:
>On quinta-feira, 3 de março de 2016 07:05:10 PST Heikkinen Jani wrote:
>> Hi,
>>
>> QtSerialBus is a technology preview in 5.6 and so on this shouldn't matter
>> that much, right? This "limitation" should be acceptable f
Dear Thiago,
Thank you very much. I will start to skip now qt modules with the -skip
configure flag to get from one error to the next one. Therefore I can't tell
you, if there would be more errors within the same module. If you guide me how
could I use your fixed sources, then I could continu
On quinta-feira, 3 de março de 2016 08:24:23 PST Olivier Goffart wrote:
> > I'm not against the principle. I am against the implementation details, as
> > Olivier's current commit has.
>
> This commit was a starting point. Of course there are implementation details
> to address.
> However, I took
On quinta-feira, 3 de março de 2016 07:05:10 PST Heikkinen Jani wrote:
> Hi,
>
> QtSerialBus is a technology preview in 5.6 and so on this shouldn't matter
> that much, right? This "limitation" should be acceptable for TPs and so on
> adding this in known issues page (https://wiki.qt.io/Qt_5.6.0_K
Am Mittwoch, 2. März 2016, 13:43:39 CET schrieb Thiago Macieira:
> On quarta-feira, 2 de março de 2016 22:34:16 PST Milian Wolff wrote:
> > On Mittwoch, 2. März 2016 12:59:30 CET Thiago Macieira wrote:
> > > On quarta-feira, 2 de março de 2016 20:59:41 PST Milian Wolff wrote:
> > > > Hey Thiago,
>
Hi,
QtSerialBus is a technology preview in 5.6 and so on this shouldn't matter that
much, right? This "limitation" should be acceptable for TPs and so on adding
this in known issues page (https://wiki.qt.io/Qt_5.6.0_Known_Issues) should be
enough?
Br,
Jani
>>-Original Message-
>>From:
The code was written for C++11 only and there isn't enough time to fix the
build issues. Therefore, it needs Qt 5.7.
I request that it be dropped from Qt 5.6 packages.
See:
https://codereview.qt-project.org/151163
https://codereview.qt-project.org/151168
Unfixed errors:
qmodbuspdu.h:163:9: war
On quinta-feira, 3 de março de 2016 00:36:34 PST rpzrpz...@gmail.com wrote:
> On 3/3/2016 12:26 AM, Thiago Macieira wrote:
> > On quinta-feira, 3 de março de 2016 00:23:45 PST rpzrpz...@gmail.com
wrote:
> >> 5.6 releases tomorrow
> >
> > No, it doesn't.
>
> http://wiki.qt.io/Qt-5.6-release
It's
On 3/3/2016 12:26 AM, Thiago Macieira wrote:
On quinta-feira, 3 de março de 2016 00:23:45 PST rpzrpz...@gmail.com wrote:
5.6 releases tomorrow
No, it doesn't.
http://wiki.qt.io/Qt-5.6-release
___
Development mailing list
Development@qt-project.o
On quinta-feira, 3 de março de 2016 00:23:45 PST rpzrpz...@gmail.com wrote:
> 5.6 releases tomorrow
No, it doesn't.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
Development mailing
With all the talk about support on 5.7 and 5.8, is 5.6 going to support
debugging under IOS 9.2 Simulator?
5.6 releases tomorrow, Qt Creator Bug 15705 not fixed.
Has anybody debugged Qt 5.6 under IOS 9.x Simulator recently?
md
On 3/3/2016 12:17 AM, Turunen Tuukka wrote:
André Somers kir
> André Somers kirjoitti 2.3.2016 kello 22.28:
>
>
>
> Op 20/02/2016 om 08:38 schreef Petroules Jake:
>> "Continue" with iOS 7? It's currently iOS 6 in both 5.7 and dev branches.
>> However, I wholeheartedly approve bumping it to 7.
>>
>> This puts us at a minimum of "last four releases" (b
On quinta-feira, 3 de março de 2016 05:45:32 PST Walter Stefan wrote:
> Dear Thiago,
>
> Thanks a lot.
>
> There are more compilation issues on CentOS 6.7 x86_64, shall I list them or
> what do you recommend?
Usually, I'd ask for bug reports, one for each. But let's have them here...
By the way
Dear Thiago,
Thanks a lot.
There are more compilation issues on CentOS 6.7 x86_64, shall I list them or
what do you recommend?
Regards,
Stefan
-Original Message-
From: Development
[mailto:development-bounces+stefan.walter=lisec@qt-project.org] On Behalf
Of Thiago Macieira
Sent: D
On quinta-feira, 3 de março de 2016 04:09:25 PST Walter Stefan wrote:
> qcanbusdevice.h:93: error: ISO C++ forbids initialization of member
> âframeIdâ
Context:
struct Filter
{
enum FormatFilter {
MatchBaseFormat = 0x0001,
MatchExtendedFormat = 0x0002,
Hi,
I am trying to build Qt 5.6.0-rc on a machine that builds Qt 5.5.1 just fine. I
am facing several compilation issues with 5.6.0-rc and will start with the
first one here.
g++ -pipe -O2 -std=c++0x -fvisibility=hidden -fvisibility-inlines-hidden
-fno-exceptions -Wall -W -D_REENTRANT -fPIC -D
On quarta-feira, 2 de março de 2016 22:34:16 PST Milian Wolff wrote:
> On Mittwoch, 2. März 2016 12:59:30 CET Thiago Macieira wrote:
> > On quarta-feira, 2 de março de 2016 20:59:41 PST Milian Wolff wrote:
> > > Hey Thiago,
> > >
> > > what is "the runtime merging problem on Windows"?
> >
> > Eve
On Mittwoch, 2. März 2016 12:59:30 CET Thiago Macieira wrote:
> On quarta-feira, 2 de março de 2016 20:59:41 PST Milian Wolff wrote:
> > Hey Thiago,
> >
> > what is "the runtime merging problem on Windows"?
>
> Ever heard of the dynamic_cast problem on Windows? It's the same.
Great, thanks a lot
On quarta-feira, 2 de março de 2016 22:38:03 PST Marc Mutz wrote:
> I think it's safe to say that range-for works as expected in so vast a
> majority of cases that the CI can be used to catch the rest. Without
> violating the Qt Code Formatting Guidelines and putting {} around each
> range-for lo
On quarta-feira, 2 de março de 2016 20:59:41 PST Milian Wolff wrote:
> Hey Thiago,
>
> what is "the runtime merging problem on Windows"?
Ever heard of the dynamic_cast problem on Windows? It's the same.
Here's the problem:
QMetaObjects are identified by their pointer addresses: two meta objects
On Wednesday 02 March 2016 17:59:05 Thiago Macieira wrote:
> On quarta-feira, 2 de março de 2016 08:52:10 PST Koehne Kai wrote:
> > Fair enough, I didn't want to imply otherwise. But I read your statement
> > as 'don't dare to use range-for unless you test with MSVC yourself',
> > which is IMO too
Op 20/02/2016 om 08:38 schreef Petroules Jake:
"Continue" with iOS 7? It's currently iOS 6 in both 5.7 and dev
branches. However, I wholeheartedly approve bumping it to 7.
This puts us at a minimum of "last four releases" (by the time 5.8 is
released) for both OS X and iOS. However I'd argue
On Mittwoch, 2. März 2016 11:28:07 CET Thiago Macieira wrote:
> On quarta-feira, 2 de março de 2016 19:24:15 PST Milian Wolff wrote:
> > On Mittwoch, 2. März 2016 09:47:33 CET Thiago Macieira wrote:
> > > On quarta-feira, 2 de março de 2016 16:48:08 PST Milian Wolff wrote:
> > > > A simple solution
On Wed, Mar 02, 2016 at 09:00:55AM -0800, Thiago Macieira wrote:
> On quarta-feira, 2 de março de 2016 08:24:50 PST Rolland Dudemaine wrote:
> > I understand that 5.7 has now reached feature freeze, but I would like
> > to ask for an exception for patches that have been pushed a few months
> > ago
On quarta-feira, 2 de março de 2016 19:24:15 PST Milian Wolff wrote:
> On Mittwoch, 2. März 2016 09:47:33 CET Thiago Macieira wrote:
> > On quarta-feira, 2 de março de 2016 16:48:08 PST Milian Wolff wrote:
> > > A simple solution would then be a macro for an explicit instantiation,
> > > similar t
On Mittwoch, 2. März 2016 09:47:33 CET Thiago Macieira wrote:
> On quarta-feira, 2 de março de 2016 16:48:08 PST Milian Wolff wrote:
> > A simple solution would then be a macro for an explicit instantiation,
> > similar to what we already do with
> > Q_DECLARE_LOGGING_CATEGORY/Q_LOGGING_CATEGORY.
On quarta-feira, 2 de março de 2016 16:48:08 PST Milian Wolff wrote:
> A simple solution would then be a macro for an explicit instantiation,
> similar to what we already do with
> Q_DECLARE_LOGGING_CATEGORY/Q_LOGGING_CATEGORY. Only there then would moc
> generate the static meta object. That shou
On quarta-feira, 2 de março de 2016 10:14:18 PST Ziller Eike wrote:
> That would break if any other code in the application (possibly in a
> different library linked to it) has e.g. using Blah = Foo;
> right?
> That sounds pretty fragile. Especially if an application loads plugins.
Correct.
You c
On Feb 19, 2016, at 11:38 PM, Petroules Jake
mailto:jake.petrou...@theqtcompany.com>> wrote:
* We require the latest Xcode toolchain and OS X on the Mac for compiling (see
separate mailing list thread). We support deployment to OS X 10.9 and later
(dropping 10.8)
+1
* On iOS, we also require
On 02.03.2016 18:00, Thiago Macieira wrote:
On quarta-feira, 2 de março de 2016 08:24:50 PST Rolland Dudemaine wrote:
Hi,
I understand that 5.7 has now reached feature freeze, but I would like
to ask for an exception for patches that have been pushed a few months
ago already but never got merge
On quarta-feira, 2 de março de 2016 08:24:50 PST Rolland Dudemaine wrote:
> Hi,
>
> I understand that 5.7 has now reached feature freeze, but I would like
> to ask for an exception for patches that have been pushed a few months
> ago already but never got merged (partially because of the CI woes).
On quarta-feira, 2 de março de 2016 08:52:10 PST Koehne Kai wrote:
> Fair enough, I didn't want to imply otherwise. But I read your statement as
> 'don't dare to use range-for unless you test with MSVC yourself', which is
> IMO too much to ask for.
>
> The rule of thumb I got is "use ranged-for w
On Mittwoch, 2. März 2016 13:48:49 CET Ziller Eike wrote:
> > On Mar 2, 2016, at 11:23 AM, Milian Wolff wrote:
> >
> > On Mittwoch, 2. März 2016 10:14:18 CET Ziller Eike wrote:
> >
> >>> On Feb 29, 2016, at 1:21 PM, Milian Wolff
> >>> wrote:
> >>>
> >>> On Friday, February 26, 2016 3:56:08 PM
> On Mar 2, 2016, at 11:23 AM, Milian Wolff wrote:
>
> On Mittwoch, 2. März 2016 10:14:18 CET Ziller Eike wrote:
>>> On Feb 29, 2016, at 1:21 PM, Milian Wolff wrote:
>>>
>>> On Friday, February 26, 2016 3:56:08 PM CET Thiago Macieira wrote:
>>>
On sexta-feira, 26 de fevereiro de 2016 20:
> On 2 Mar 2016, at 09:37, Welbourne Edward
> wrote:
>
> Andreas Hartmetz said:
>> Arcminutes are a really good idea. The size of screen elements isn't
>> really about physical dimensions, it's about size on retina (the
>> actual biological thing ;) really, or legibility.
> [...]
>> If the syst
I have a complex mixed QML and C++ desktop application where I get crashes
when closing the program.
I use Qt-5.5.1/msvc2013 (32 bit) on Windows 7.
I did not yet report a bug because I could not produce a small sample
program to reproduce the bug.
The problem seems to be a double free of the OpenG
On Mittwoch, 2. März 2016 10:14:18 CET Ziller Eike wrote:
> > On Feb 29, 2016, at 1:21 PM, Milian Wolff wrote:
> >
> > On Friday, February 26, 2016 3:56:08 PM CET Thiago Macieira wrote:
> >
> >> On sexta-feira, 26 de fevereiro de 2016 20:30:28 PST Milian Wolff wrote:
> >>
> The main proble
On Friday 26 February 2016 19:07:53 Nurmi J-P wrote:
> Hi Lars,
>
> > On 27. jan. 2016, at 09.30, Knoll Lars
> > wrote:
> >
> > If anybody else has a feature he believes absolutely has to make it to
> > 5.7, get it done until Monday or talk to me :)
> I would like to ask for an exception for tex
> On Feb 29, 2016, at 1:21 PM, Milian Wolff wrote:
>
> On Friday, February 26, 2016 3:56:08 PM CET Thiago Macieira wrote:
>> On sexta-feira, 26 de fevereiro de 2016 20:30:28 PST Milian Wolff wrote:
The main problems of templated QObject are captured more or less in
this
thre
Ok, go for it.
Cheers,
Lars
On 02/03/16 09:54, "Development on behalf of Eskil Abrahamsen Blomfeldt"
wrote:
>
>
>Den 26.02.2016 20:07, skrev Nurmi J-P:
>> Hi Lars,
>>
>>> On 27. jan. 2016, at 09.30, Knoll Lars wrote:
>>>
>>> If anybody else has a feature he believes absolutely has to make
It never worked in the Qt5.x releases so far. For what it's worth I'd argue
this is bugfixing for a non-working platform.
Your gerrit reviews would have to be retargeted to 5.7 (A Gerrit admin can do
that if that's the conclusion we come to in this thread).
--
Alex
> -Original Message--
Den 26.02.2016 20:07, skrev Nurmi J-P:
Hi Lars,
On 27. jan. 2016, at 09.30, Knoll Lars wrote:
If anybody else has a feature he believes absolutely has to make it to 5.7, get
it done until Monday or talk to me :)
I would like to ask for an exception for text selection handles. It's a cruci
> -Original Message-
> From: Development [mailto:development-
> bounces+kai.koehne=theqtcompany@qt-project.org] On Behalf Of
> Thiago Macieira
> Sent: Tuesday, March 01, 2016 4:23 PM
> To: development@qt-project.org
> Subject: Re: [Development] Q_COMPILER_RANGE_FOR not supported
> by/de
Andreas Hartmetz said:
> Arcminutes are a really good idea. The size of screen elements isn't
> really about physical dimensions, it's about size on retina (the
> actual biological thing ;) really, or legibility.
[...]
> If the system had "known" that the typical user to screen distance was
> 2-3 m
Am Freitag, 26. Februar 2016, 19:07:53 CET schrieb Nurmi J-P:
> I would like to ask for an exception for text selection handles. It's a
> crucial feature to make the new editor controls usable on mobile and
> embedded. There's a task for qtquickcontrols2
> (https://bugreports.qt.io/browse/QTBUG-510
Ideally i'd like to get those also in 5.7 indeed.
For 5.8/dev, there is no need for asking for an exception i guess, just
following the regular merge procedure would do just fine.
--Rolland
From: Liang Qi
Sent: Mar 2, 2016 08:28
To: Rolland Dudemaine
Cc: development@qt-project.org
Subject: Re:
>On 2016-03-01, Milian Wolff wrote:
>> b) Apparently there are never any debug symbols shipped for the release build
>> fo Qt. Having debug symbols even for a release build is crucial for a good
>> profiling experience. Could we maybe get release builds in the future with -
>> force-debug-info t
50 matches
Mail list logo
