> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Thiago Macieira
> Sent: Thursday, July 21, 2016 10:51 PM
> To: development@qt-project.org
> Subject: Re: [Development] Remember to rebuild qmake in dev
>
> On quinta-feir
On quinta-feira, 21 de julho de 2016 20:23:19 PDT Oswald Buddenhagen wrote:
> On Thu, Jul 21, 2016 at 09:27:58AM -0700, Thiago Macieira wrote:
> > moc.prf with MSVC now depends on a side feature in qmake to help support
> > generating the moc_predefs.h file. If you're using MSVC, please remember
>
On quinta-feira, 21 de julho de 2016 18:02:51 PDT Mitch Curtis wrote:
> It's probably worth pointing out what kind of errors we can expect should we
> forget (so that we can recognise the problem).
The moc_predefs.h file contains qmake's help output, as opposed to a valid C
source file. Since tha
Hello, Everyone and Thiago.
>> SVG icons are not shown at all in static builds of Qt, but png icons are
>> fine (both icons are taken from resorse file). Static and shred Qt 5.6.1
>> build were done with same config settings except of cause "static".
> Remember to force the inclusion of the svg i
On Thu, Jul 21, 2016 at 09:27:58AM -0700, Thiago Macieira wrote:
> moc.prf with MSVC now depends on a side feature in qmake to help support
> generating the moc_predefs.h file. If you're using MSVC, please remember to
> recompile qmake soon.
>
a much better recommendation is "run config.status (
It's probably worth pointing out what kind of errors we can expect should we
forget (so that we can recognise the problem).
From: Development on
behalf of Thiago Macieira
Sent: Thursday, 21 July 2016 6:27:58 PM
To: development@qt-project.org
Subject: [D
Hello
moc.prf with MSVC now depends on a side feature in qmake to help support
generating the moc_predefs.h file. If you're using MSVC, please remember to
recompile qmake soon.
This does not affect GCC (any OS) or the Intel compiler (any OS), as both
support the "dump macros" hidden feature. I
On quinta-feira, 21 de julho de 2016 15:19:38 PDT Boudewijn Rempt wrote:
> I just found that qtbase-opensource-src-5.6.1-1.tar.xz
> unpacks to qtbase-opensource-src-5.6.1, which completely
> breaks any automated system like mxe (mxe.cc) which depends
> on the foldername being the same tarball name.
On quinta-feira, 21 de julho de 2016 17:05:42 PDT Prav wrote:
> But this field is CHANGEBLE! So Fix Version SHOULD NOT BE KNOWN. It is how
> maintainer see planning of it currently.
That is not how we use the bug tracker, as I've explained. The rest of your
email is not relevant.
--
Thiago Maci
On quinta-feira, 21 de julho de 2016 14:31:55 PDT Prav wrote:
> Here is also one important detail. If Denis need to decide to hire someone
> he need information about plans of fixing the bug. If he need to wait 1/2
> year to get estimation that this bug is not going to be fixed in nearest
> months
On quinta-feira, 21 de julho de 2016 10:20:59 PDT Prav wrote:
> Hello, Everyone.
>
> > Bugs are fixed when they are fixed. You won't get any estimate before the
> > developer actually starts fixing the issue. And even then, it may take
> > months or more until it actually gets fixed.
>
> Agree bu
Op 21/07/2016 om 16:35 schreef Sze Howe Koh:
On 21 July 2016 at 19:04, Mitch Curtis wrote:
Hello.
Stack Overflow Documentation is now in Beta. You can read more about it here:
http://stackoverflow.com/tour/documentation
It is much more accessible than our contribution system, so I see a lo
On Thu, Jul 21, 2016, at 04:05 PM, Prav wrote:
> Agree with you if this field was unchangeable once it was set (nobody
> knows the future exactly ... ).
> But this field is CHANGEBLE! So Fix Version SHOULD NOT BE KNOWN. It is
> how maintainer see planning of it currently.
Looking at my current wor
> -Original Message-
> From: Development [mailto:development-bounces+mitch.curtis=qt.io@qt-
> project.org] On Behalf Of Prav
> Sent: Thursday, 21 July 2016 4:06 PM
> To: development@qt-project.org
> Subject: Re: [Development] [QtMultimedia] Still is supported, active?
>
> Hello, Everyone
On 21 July 2016 at 19:04, Mitch Curtis wrote:
> Hello.
>
> Stack Overflow Documentation is now in Beta. You can read more about it here:
>
> http://stackoverflow.com/tour/documentation
>
> It is much more accessible than our contribution system, so I see a lot of
> documentation/example contribut
Hello, Everyone.
>> If "Fix Version" is filled by Yoann Lopes 6 months ago then he will get
>> this estimation and can decide to hire Woboq or someone else to fix or
>> whatever.
> This is an unreasonable expectation to place on developers. For
> blockers (which, as far as I understand, this was
I just found that qtbase-opensource-src-5.6.1-1.tar.xz
unpacks to qtbase-opensource-src-5.6.1, which completely
breaks any automated system like mxe (mxe.cc) which depends
on the foldername being the same tarball name.
Was this intentional, or just an oversight?
--
Boudewijn Rempt | http://www.k
> -Original Message-
> From: Development [mailto:development-bounces+mitch.curtis=qt.io@qt-
> project.org] On Behalf Of Prav
> Sent: Thursday, 21 July 2016 1:32 PM
> To: development@qt-project.org
> Subject: Re: [Development] [QtMultimedia] Still is supported, active?
>
> Hello, Everyone
Hello, Everyone.
> If you want this bug fixed, or to improve the QtMM quality there are far
> better ways:
> - Get a Qt support license from the Qt Company and raise the issue
> to them. They very often help raising important customer issues like
> this one to P1 since in the end, it's that mone
I can't check if the uboot is too old because board can't boot itself when i
use flashboot image of Qt. So I can't update uboot from sd card too. It does
nothing basically.
Also uboot is working at yocto images if it shows it is okay.
Gönderen: Bahadır Can
Gön
Hello.
Stack Overflow Documentation is now in Beta. You can read more about it here:
http://stackoverflow.com/tour/documentation
It is much more accessible than our contribution system, so I see a lot of
documentation/example contributions going there instead of to Gerrit.
I also wonder if we
Hello, Everyone.
>> So while I agree that angriness is not helpful for mail list ... messages
>> like this
>> are probably the seed to rethink strategy of working with bugs.
> Somewhat a side remark, but the unfortunate consequence of this thinking is
> that the objectively best way to get a lot
Title: Re: [Qt-creator] [Windows] Qt Versions/Kit auto-detection doesn't work on snapshots
Hello, Julius.
I noticed a strange behavior on snapshots for a while now. Neither Qt versions nor kits are detected at all.
With Creator 4.0.x, everything works perfectly (Qt 5.6.1 & Qt 5.7, MinGW an
> On 21 Jul 2016, at 11:01, Denis Shienkov wrote:
>
> @ Thiago,
>
> >The one you linked to is P2 - Important. It's neither critical nor
> showstopper.
>
> It isn't I did the decision about assigning the P2 status. I personally would
> establish P0/P1 if it would make sense (but, it is just "e
@ Thiago,
>The one you linked to is P2 - Important. It's neither critical nor
showstopper.
It isn't I did the decision about assigning the P2 status. I personally
would establish P0/P1 if it would make sense (but, it is just "empty work"
which won't change anything).
Since many bugs with P1 statu
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> [...]
> So while I agree that angriness is not helpful for mail list ... messages
> like this
> are probably the seed to rethink strategy of working with bugs.
Somewhat a side remark, but the unfor
Hello, Everyone.
> Bugs are fixed when they are fixed. You won't get any estimate before the
> developer actually starts fixing the issue. And even then, it may take months
> or more until it actually gets fixed.
Agree but devil is in details. Currently there is a practice to not fill-out
necess
> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Thiago Macieira
> Sent: Wednesday, July 20, 2016 6:57 PM
> To: development@qt-project.org
> Subject: Re: [Development] Documenting 3rd party code Qt
>
> On quarta-feira,
28 matches
Mail list logo
