69
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Tue, Feb 11, 2020 at 03:15:11PM +, Vitaly Fanaskov wrote:
> I want to summarize intermediate results of the discussion and return it
> back to the track.
>
>
> Subject: using smart pointers in the API.
> Good idea. Better to use than not because of automatic lifetime
> management,
*shru
Not in the CI yet. Was polishing things locally. But should add that soon.
> On 11. Feb 2020, at 16:56, Kyle Edwards wrote:
>
> Great news!
>
> Are you using Ninja Multi-Config yet? :)
>
> Kyle
>
> On Tue, Feb 11, 2020 at 10:40 AM Alexandru Croitor
> wrote:
>>
>> I published the Qt 6 CMake
Great news!
Are you using Ninja Multi-Config yet? :)
Kyle
On Tue, Feb 11, 2020 at 10:40 AM Alexandru Croitor
wrote:
>
> I published the Qt 6 CMake Port slides that I presented at Qt Contributor
> Summit in 2019.
>
> https://github.com/alcroito/qt6_cmake_port_slides
>
> It might be a bit outdat
I published the Qt 6 CMake Port slides that I presented at Qt Contributor
Summit in 2019.
https://github.com/alcroito/qt6_cmake_port_slides
It might be a bit outdated compared to today's state, but still has some useful
info to ease into the whole thing as an alternative to the cmake/READMEmd.
Great! Thanks for the heads up!
Tor Arne
> On 11 Feb 2020, at 16:17, Alexandru Croitor wrote:
>
> Hi,
>
> Short PSA.
>
> The merge of wip/cmake to dev is done.
>
> I'm enabling enforcing CMake builds in dev branch. CMake build phase will
> have to pass , tests can still fail and it won't f
Hi,
Short PSA.
The merge of wip/cmake to dev is done.
I'm enabling enforcing CMake builds in dev branch. CMake build phase will have
to pass , tests can still fail and it won't fail integrations.
In case some build system .pro change sneaks in between the merge and the
enabling of enforcing C
I want to summarize intermediate results of the discussion and return it
back to the track.
Subject: using smart pointers in the API.
Good idea. Better to use than not because of automatic lifetime
management, explicit ownership semantics, and code base maintainability
is simpler. However, it
Great! Hopefully the remaining steps towards alpha go nicely.
There are quite a few items not yet listed at:
https://wiki.qt.io/New_Features_in_Qt_5.15
The new feature highlight is valuable for users, so please lift a few of the
key items for each module into the list. Think what are the mos
> On 10 Feb 2020, at 13:44, Jani Heikkinen wrote:
>
> Hi all,
>
> It seems that there is still some work needed to finalize deprecations and
> replacement for Qt 5.15
>
> We had some discussion here in Qt Company and based on that I propose:
>
> - Let's put Alpha out after this header view fe
10 matches
Mail list logo
