29.11.2016, 10:43, "Jake Petroules" :
> I don't know what sort of cross build and deployment environment you've set
> up, but I've worked with Qt Creator developing on actual embedded Linux
> hardware and the code-deploy-test cycle is lightning fast; no slower than
> desktop at all.
Indeed. T
As for embedded Linux it’s not only the build and deployment itself (I usually
have a separate VM for each customer and board), but much more the nature of
the device itself. On the target all „real“ interfaces and features are
enabled. On the desktop I disable them to speed things up and/or to
I don't know what sort of cross build and deployment environment you've set up,
but I've worked with Qt Creator developing on actual embedded Linux hardware
and the code-deploy-test cycle is lightning fast; no slower than desktop at all.
iOS may be slower in particular due to our suboptimal buil
I don’t get the use case for having *only* iOS installed on my system. As well
as for example only a cross Qt for an embedded device (iOS is practically the
same thing). The normal development cycle should be (at least in my opinion)
mainly develop on the desktop and check on the target in a reg
> On Nov 28, 2016, at 11:24 PM, Jani Heikkinen wrote:
>
>> -Original Message-
>> From: Development [mailto:development-
>> bounces+jani.heikkinen=qt...@qt-project.org] On Behalf Of Jake Petroules
>> Sent: maanantaina 28. marraskuuta 2016 20.23
>> To: Alexander Blasche
>> Cc: development
> -Original Message-
> From: Development [mailto:development-
> bounces+jani.heikkinen=qt...@qt-project.org] On Behalf Of Jake Petroules
> Sent: maanantaina 28. marraskuuta 2016 20.23
> To: Alexander Blasche
> Cc: development@qt-project.org; releas...@qt-project.org
> Subject: Re: [Develop
> On Nov 28, 2016, at 7:40 AM, Alexander Blasche
> wrote:
>
> Ok, let's summarize and restate the package list for Qt 5.9 based on the
> comments provided on this mail thread. The list describes the delta to Qt 5.8
> packages:
>
> * For macOS we drop 10.9 and support 10.10, 10.11 & 10.12
> *
Ok, let's summarize and restate the package list for Qt 5.9 based on the
comments provided on this mail thread. The list describes the delta to Qt 5.8
packages:
* For macOS we drop 10.9 and support 10.10, 10.11 & 10.12
* For iOS we drop 7.x and support 8.x, 9.x, 10.x
* MinGW remains 5.3 using 32
On 2016-11-18 20:37, Marc Mutz wrote:
On Friday 18 November 2016 09:30:03 Lars Knoll wrote:
On 17/11/16 23:03, Thiago Macieira wrote:
[...]
>But GSL is another story. If it is sensibly developed, with a promise
>to binary compatibility for extended periods of time and no nonsense
>
Hello,
Currently, MinGW builds in Coin use -system-zlib configuration. It happens
because MinGW is shipped with zlib headers and libz.a. However, linking zlib
to several Qt modules (at least, QtCore, QtGui, QtNetwork, and QtSvg) is
suboptimal, while with -system-zlib one copy in QtCore is shared b
Il 25/11/2016 18:45, Oswald Buddenhagen ha scritto:
> as an immediate measure, you may step up and _commit to_ being the merge
> monkey (at least for the 5.6 -> 5.8 merges). if you do that quick enough
> (like, monday), we may reconsider.
Nice straw man in there. :P
I put "merge masters burden" i
On Friday 25 November 2016 13:40:15 Oswald Buddenhagen wrote:
> hello,
>
> as discussed at the QtCS and these lists, forward-merging from the LTS
> branch 5.6 is becoming a significant burden.
> therefore, 5.6 is switching to a cherry-pick based model:
> - 5.6 is *NOT* going to be forward-merged a
Hi Ossi/Friedeman,
could you retarget the following to the 5.8.0 branch please?
Thanks in advance!
https://codereview.qt-project.org/#/c/170339/
https://codereview.qt-project.org/#/c/170431/
https://codereview.qt-project.org/#/c/170432/
https://codereview.qt-project.org/#/c/170433/
https://coder
13 matches
Mail list logo
