On domingo, 18 de setembro de 2016 19:59:24 PDT Holger Freyther wrote:
> > On 18 Sep 2016, at 17:12, Marc Mutz wrote:
> >
> >
> > This is another issue. This week's report only contains issues in code
> > built by qmake, probably caused by the configure problem you mention.
> On 18 Sep 2016, at 17:12, Marc Mutz wrote:
>
>
> This is another issue. This week's report only contains issues in code built
> by qmake, probably caused by the configure problem you mention.
>
> Last week's report, to which Peppe referred, however, contained all of
>
On Saturday 17 September 2016 09:51:02 Holger Freyther wrote:
> > On 15 Sep 2016, at 14:51, Giuseppe D'Angelo
> > wrote:
> >
> > Howdy,
>
> Hi!
>
> > while playing around with Coverity Scan with a few colleagues of mine we
> > noticed that only qtbase is getting
On domingo, 18 de setembro de 2016 22:22:57 PDT Oswald Buddenhagen wrote:
> On Sat, Sep 17, 2016 at 12:49:36PM -0700, Thiago Macieira wrote:
> > So how am I going to reconfigure qtbase once I've built the rest of qt5?
>
> you don't. you keep configuring qt5, or you clean out the non-qtbase
>
> On Sep 18, 2016, at 4:44 PM, Thiago Macieira
> wrote:
>
> On domingo, 18 de setembro de 2016 22:22:57 PDT Oswald Buddenhagen wrote:
>> On Sat, Sep 17, 2016 at 12:49:36PM -0700, Thiago Macieira wrote:
>>> So how am I going to reconfigure qtbase once I've built the
On Sat, Sep 17, 2016 at 12:49:36PM -0700, Thiago Macieira wrote:
> So how am I going to reconfigure qtbase once I've built the rest of qt5?
>
you don't. you keep configuring qt5, or you clean out the non-qtbase
artifacts first.
> My workflow is:
>
you should consider yourself lucky that this
On segunda-feira, 19 de setembro de 2016 00:22:42 PDT Jake Petroules wrote:
> > It's worked for over 4 years. I may not be the only one doing this.
> >
> > Please fix it.
>
> I don't see why we should, it seems an illogical workflow to configure qt5
> and then expect to be able to configure from
Hi,
Recently, a few unit test failures[1] in the (unreleased) QtPIM module
showed that the recent change[2] which changes the semantics of null
assignment (from JS) to a QVariant Q_PROPERTY can affect existing client
code.
Certainly, the cases which are affected are most likely edge-cases (that