Re: [Development] Short QDateTime optimisation

02.05.2016, 10:44, "Thiago Macieira" : > Hello > > https://codereview.qt-project.org/157714 > > I've just pushed one large commit that changes QDateTime to support a "short > QDateTime Optimisation". Inspired by the SSO mechanism used in libc++ and > similar to what

Re: [Development] Short QDateTime optimisation

On segunda-feira, 2 de maio de 2016 08:26:26 PDT Jake Petroules wrote: > Too bad, I thought I could have helped you here but the MIPS board I just > bought is LE. > > You could always try Debian mips or ppc in qemu. They have prebuilt images. Don't have time for that. I'll do a review of the

Re: [Development] Retiring libtiff too

On segunda-feira, 2 de maio de 2016 10:46:53 PDT Lars Knoll wrote: > Well, on Linux these libraries are nicely available on the system. But it > does not help us on Windows, where we do have to ship these libraries if we > want to provide something that's easy to use for our users/customers. Let

Re: [Development] Short QDateTime optimisation

On segunda-feira, 2 de maio de 2016 19:07:24 PDT Konstantin Tokarev wrote: > Do you mean 64-bit big-endian system, or both 32-bit and 64-bit? 64-bit big endian. On 32-bit it should not enable the optimisation because 32 bits aren't enough bits. -- Thiago Macieira - thiago.macieira (AT)

Re: [Development] Retiring libtiff too

On 02/05/16 17:52, "Development on behalf of Thiago Macieira" wrote: >On segunda-feira, 2 de maio de 2016 10:46:53 PDT Lars Knoll wrote: >> Well, on Linux these libraries are nicely available on the

Re: [Development] Retiring libtiff too

On segunda-feira, 2 de maio de 2016 18:07:29 PDT Lars Knoll wrote: > >> So while I don't like us having copies of these libraries in our > >> repositories, not shipping any support for these image formats in our > >> packages is not a good option neither. > > > >I kinda disagree. I would prefer an

Re: [Development] Retiring libtiff too

On sexta-feira, 29 de abril de 2016 21:14:17 PDT Allan Sandfeld Jensen wrote: > Do you have any citations for these issues? CVE-2014-9655 CVE-2015-1547 CVE-2015-8665 CVE-2015-8683 CVE-2015-7554 CVE-2015-8668 -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open

Re: [Development] Qt QuickLook plugin

> On May 1, 2016, at 01:47, Jake Petroules wrote: > > That would be pretty awesome. It's possible we could ship it inside of Qt > Creator? You can put them in either ~/Library/QuickLook or in > $BUNDLE_CONTENTS/Library/QuickLook That made me start wondering why I do see

[Development] Short QDateTime optimisation

Hello https://codereview.qt-project.org/157714 I've just pushed one large commit that changes QDateTime to support a "short QDateTime Optimisation". Inspired by the SSO mechanism used in libc++ and similar to what we've done to QVersionNumber, I've made QDateTime not allocate memory for most

Re: [Development] Short QDateTime optimisation

On May 1, 2016, at 7:35 PM, Thiago Macieira > wrote: Hello https://codereview.qt-project.org/157714 I've just pushed one large commit that changes QDateTime to support a "short QDateTime Optimisation". Inspired by the SSO mechanism

Re: [Development] Qt CI reliability

On Saturday 30 of April 2016 20:26:20 Sean Harmer wrote: > Hi, Hi, > after yet another 5 hour wait just to be greeted with yet another random > failure with no build logs I'm getting really tired of the poor reliability > of the Qt CI system. I'm sorry about that. >

Re: [Development] Retiring libtiff too

On 30/04/16 12:22, "Development on behalf of Richard Moore" on behalf of r...@kde.org> wrote: On 29 April 2016 at 20:14, Allan Sandfeld Jensen

[Development] Scope of source code license files

Hello, The LICENSE.GPLvX and LICENSE.LGPLvX files from http://code.qt.io/cgit/qt/qtbase.git/tree/ (and submodules) start with "The Qt Toolkit is Copyright (C) 2015...", but then they go on to say "You may use, distribute and copy the Qt GUI Toolkit under the terms of..." Is this correct? What