> On 4 May 2017, at 16:51, Sergio Martins wrote:
>
> On 2017-05-04 15:18, Thiago Macieira wrote:
>> Em quinta-feira, 4 de maio de 2017, às 06:58:53 PDT, Konstantin Tokarev
>> escreveu:
>>> But we could have Linux clang configuration with clazy plugin.
>> Why? Clazy is
On 2017-05-04 15:18, Thiago Macieira wrote:
Em quinta-feira, 4 de maio de 2017, às 06:58:53 PDT, Konstantin Tokarev
escreveu:
But we could have Linux clang configuration with clazy plugin.
Why? Clazy is not part of our development philosophy. We should only do
that
after there's a QUIP
Em quinta-feira, 4 de maio de 2017, às 07:34:34 PDT, Sergio Martins escreveu:
> On 2017-05-04 14:53, Thiago Macieira wrote:
> > Em quinta-feira, 4 de maio de 2017, às 00:23:46 PDT, Heikki Halmet
> >
> > escreveu:
> >> Clang 4: Do we really need this to be tested with Linux in CI? If yes,
> >>
On 2017-05-04 14:53, Thiago Macieira wrote:
Em quinta-feira, 4 de maio de 2017, às 00:23:46 PDT, Heikki Halmet
escreveu:
Clang 4: Do we really need this to be tested with Linux in CI? If yes,
then
which configuration it will be replaced?
I don't think we need to. The macOS builds should be
Em quinta-feira, 4 de maio de 2017, às 06:58:53 PDT, Konstantin Tokarev
escreveu:
> But we could have Linux clang configuration with clazy plugin.
Why? Clazy is not part of our development philosophy. We should only do that
after there's a QUIP explaining which options in Clazy we use (which
04.05.2017, 16:53, "Thiago Macieira" :
> Em quinta-feira, 4 de maio de 2017, às 00:23:46 PDT, Heikki Halmet escreveu:
>> Clang 4: Do we really need this to be tested with Linux in CI? If yes, then
>> which configuration it will be replaced?
>
> I don't think we need
Em quinta-feira, 4 de maio de 2017, às 00:23:46 PDT, Heikki Halmet escreveu:
> Clang 4: Do we really need this to be tested with Linux in CI? If yes, then
> which configuration it will be replaced?
I don't think we need to. The macOS builds should be sufficient for almost
everything intrinsic to
] On Behalf Of
Tuukka Turunen
Sent: 2. toukokuuta 2017 10:23
To: Jake Petroules <jake.petrou...@qt.io>; Lars Knoll <lars.kn...@qt.io>
Cc: Qt development mailing list <development@qt-project.org>
Subject: Re: [Development] Proposal for Qt 5.10 platforms and configurations
changes
Hi,
Hi,
While I do agree that having a platform in CI and supporting it for those who
have purchased support are not 1:1, in case of dropping the 32-bit iOS from CI
for Qt 5.10 it also means that this configuration should no longer be used and
not be supported. I do not see much problems with
On Saturday, 29 April 2017 19:14:54 -03 Mat Sutcliffe wrote:
> It also controls whether Q_DECL_CONSTEXPR expands to constexpr or nothing.
> But I don't think that should alter whether or not a function is inline,
> because functions declared with Q_DECL_CONSTEXPR should already be inline
> anyway.
On 29 April 2017 at 21:31, Thiago Macieira
wrote:
> On Friday, 28 April 2017 12:50:41 -03 Mat Sutcliffe wrote:
> > tldr: MSVC expects to see linker symbols for inline member functions of
> > exported classes. When such a function is defined within #ifdef
> >
On Friday, 28 April 2017 12:50:41 -03 Mat Sutcliffe wrote:
> tldr: MSVC expects to see linker symbols for inline member functions of
> exported classes. When such a function is defined within #ifdef
> Q_COMPILER_foo (being a macro that is defined for 2017 but not 2015) this
> could mean linker
> On Apr 27, 2017, at 11:28 PM, Lars Knoll wrote:
>
>
>> On 27 Apr 2017, at 16:59, Jake Petroules wrote:
>>
>>>
>>> On Apr 27, 2017, at 7:07 AM, Tuukka Turunen wrote:
>>>
>>>
>>> Hi,
>>>
>>> Related to the Apple platforms,
> On Apr 27, 2017, at 11:54 PM, Shawn Rutledge wrote:
>
>
>> On 27 Apr 2017, at 16:59, Jake Petroules wrote:
>>
>> Anyways, iOS 11 will likely drop support for 32-bit applications entirely
>> (i.e. they will not launch because 32-bit system libs
On Friday, 28 April 2017 09:51:58 -03 Benjamin TERRIER wrote:
> 2017-04-28 14:23 GMT+02:00 Thiago Macieira :
> > On Friday, 28 April 2017 03:56:22 -03 Jani Heikkinen wrote:
> >> Yes, MSVC 2017 is already supported in Qt 5.9 and we are trying to get
> >> pre-built
On 28 April 2017 at 13:51, Benjamin TERRIER wrote:
> 2017-04-28 14:23 GMT+02:00 Thiago Macieira :
> > On Friday, 28 April 2017 03:56:22 -03 Jani Heikkinen wrote:
> >> Yes, MSVC 2017 is already supported in Qt 5.9 and we are trying to get
> >>
2017-04-28 14:23 GMT+02:00 Thiago Macieira :
> On Friday, 28 April 2017 03:56:22 -03 Jani Heikkinen wrote:
>> Yes, MSVC 2017 is already supported in Qt 5.9 and we are trying to get
>> pre-built binaries available before final release; let's see if we can
>> make it
On Friday, 28 April 2017 03:56:22 -03 Jani Heikkinen wrote:
> Yes, MSVC 2017 is already supported in Qt 5.9 and we are trying to get
> pre-built binaries available before final release; let's see if we can
> make it happen
I remember a discussion about whether we needed MSVC 2017 binaries in the
>> Something like the following seems nice:
>> Tier 1 - the most rigorously tested configurations, tested in CI
>> Tier 2 - we actively try to make it work but it's a lower priority;
>> will make and accept patches and provide support but isn't tested in
>> CI
>> Unsupported - we remove code
org> on
behalf of Wolfgang Baron <wolfgang.ba...@gmx.net>
Sent: Friday, April 28, 2017 12:03 AM
To: Liang Qi
Cc: development@qt-project.org
Subject: Re: [Development] Proposal for Qt 5.10 platforms and configurations
changes
HI,
Am 27.04.2017 um 22:54 schrieb Liang Qi:
On 27 April 2017 at 22:
> On 27 Apr 2017, at 16:59, Jake Petroules wrote:
>
> Anyways, iOS 11 will likely drop support for 32-bit applications entirely
> (i.e. they will not launch because 32-bit system libs will be GONE). So I
> agree we should stop shipping 32-bit slices in our binary
Hi,
Exactly cutting down the time it takes for the CI to complete a build of all of
Qt is one of the motivation factors. And note how in dev (and bus 5.10) we are
spending extra time building for WatchOS and TvOS, so it would seem like a
trade to me ;)
Simon
On 28. Apr 2017, at 08:28, Lars
Hi Jake,
On joi, 27 aprilie 2017 15:00:58 EEST Jake Petroules wrote:
> > On Apr 27, 2017, at 7:40 AM, BogDan Vatra wrote:
> >
> > For Android I'd like to support 64 bit platforms (arm and x86)
>
>
> They are already supported. Feel free to compile Qt with the
On 27 Apr 2017, at 16:59, Jake Petroules
> wrote:
On Apr 27, 2017, at 7:07 AM, Tuukka Turunen
> wrote:
Hi,
Related to the Apple platforms, could we consider the following for Qt 5.10:
- Drop
Il 27/04/2017 23:37, Thiago Macieira ha scritto:
> Because if you mean the former, it's already supported in 5.8.
But not in 5.8.0. So, effectively, in no released 5.8 version.
[grumbles]
Cheers,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (UK) Ltd., a KDAB
On Thursday, 27 April 2017 18:03:32 -03 Wolfgang Baron wrote:
> Thanks, I didn't see that and don't see a "msvc2017 64-bit" for "Qt 5.9
> Beta2" in the online installer, so I was afraid it would not be in the
> release either. Good to hear it will be there for the release!
There's no need. You
On Thursday, 27 April 2017 17:50:08 -03 Wolfgang Baron wrote:
> Hi,
>
> I would like to see msvc_2017 support on the Windows plattform for any
> version as soon as possible.
Do you mean "support" as in "it works" or as in "it's tested in the CI".
Because if you mean the former, it's already
HI,
Am 27.04.2017 um 22:54 schrieb Liang Qi:
On 27 April 2017 at 22:50, Wolfgang Baron > wrote:
Hi,
I would like to see msvc_2017 support on the Windows plattform for
any version as soon as possible.
That will happen soon
On 27 April 2017 at 22:50, Wolfgang Baron wrote:
> Hi,
>
> I would like to see msvc_2017 support on the Windows plattform for any
> version as soon as possible.
That will happen soon in 5.9, please follow up
https://codereview.qt-project.org/#/c/191981/ and etc.
Hi,
I would like to see msvc_2017 support on the Windows plattform for any
version as soon as possible.
Best regards,
Wolfgang Baron
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Thursday, 27 April 2017 09:02:33 -03 Ville Voutilainen wrote:
> That's because GCC 7 hasn't been released yet, but it will be soon,
> and then it will be in almost every linux distro as a system
> compiler before we ship Qt 5.10, so I think it would be quite wise to
> have it in CI as soon as
> On Apr 27, 2017, at 7:40 AM, BogDan Vatra wrote:
>
> For Android I'd like to support 64 bit platforms (arm and x86)
They are already supported. Feel free to compile Qt with the appropriate -arch
options. Do you mean you want them in CI and want us to start shipping
> On Apr 27, 2017, at 7:07 AM, Tuukka Turunen wrote:
>
>
> Hi,
>
> Related to the Apple platforms, could we consider the following for Qt 5.10:
> - Drop the older iPhone support by removing ARMv7 from iOS
>
For Android I'd like to support 64 bit platforms (arm and x86)
BogDan.
On April 27, 2017 12:29:08 PM GMT+03:00, Heikki Halmet
wrote:
>Hi,
>
>
>
>Below we have proposal for changes in supported platforms and
>configurations from Qt 5.9 to 5.10.
>
>Please comment if the
The mkspecs are there. https://codereview.qt-project.org/#/c/192579/ is
needed to make them work (again).
On 2017-04-27, 8:07 AM, "Development on behalf of Stottlemyer, Brett
(B.S.)" wrote:
>> Please
ukka.turu...@qt.io>
Sent: Thursday, April 27, 2017 4:07:48 PM
To: Jake Petroules; Heikki Halmet; development@qt-project.org
Subject: Re: [Development] Proposal for Qt 5.10 platforms and configurations
changes
Hi,
Related to the Apple platforms, could we consider the following for Qt 5.10:
- Drop the
Hi,
Related to the Apple platforms, could we consider the following for Qt 5.10:
- Drop the older iPhone support by removing ARMv7 from iOS
(http://dorianroy.com/blog/wp-content/uploads/2016/09/iOS_Support_Matrix_v4.2.pdf)
- Consider also dropping ARMv7s support, which would allow dropping i386
> Please refer to Qt 5.9 Supported platforms ->
> http://doc-snapshots.qt.io/qt5-5.9/supported-platforms.html
That page has the following for QNX: “QNX 6.6.0, 7.0 (armv7le and x86)”
As QNX 7.0 includes 64-bit support, are aarch64le and x86_64 supported on 5.9?
If not, can they be added for
On 27 April 2017 at 14:58, Shawn Rutledge wrote:
> Giuseppe was asking on IRC for GCC 7 and Clang 4. Which are quite bleeding
> edge for almost all distros at this point, I suppose; Arch recently got Clang
> 4 but not GCC 7 yet.
That's because GCC 7 hasn't been released
> On 27 Apr 2017, at 11:29, Heikki Halmet wrote:
>
> Hi,
>
> Below we have proposal for changes in supported platforms and configurations
> from Qt 5.9 to 5.10.
> Please comment if the proposal is insufficient or the changes are
> unacceptable somehow.
>
> Please
> On Apr 27, 2017, at 2:29 AM, Heikki Halmet wrote:
>
> Hi,
>
> Below we have proposal for changes in supported platforms and configurations
> from Qt 5.9 to 5.10.
> Please comment if the proposal is insufficient or the changes are
> unacceptable somehow.
>
> Please
Hi,
Below we have proposal for changes in supported platforms and configurations
from Qt 5.9 to 5.10.
Please comment if the proposal is insufficient or the changes are unacceptable
somehow.
Please refer to Qt 5.9 Supported platforms ->
42 matches
Mail list logo