Great news!

Are you using Ninja Multi-Config yet? :)

Kyle

On Tue, Feb 11, 2020 at 10:40 AM Alexandru Croitor
<alexandru.croi...@qt.io> 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 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.
>
> > On 11. Feb 2020, at 16:29, Tor Arne Vestbø <tor.arne.ves...@qt.io> wrote:
> >
> > Great! Thanks for the heads up!
> >
> > Tor Arne
> >
> >> On 11 Feb 2020, at 16:17, Alexandru Croitor <alexandru.croi...@qt.io> 
> >> 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 fail integrations.
> >>
> >> In case some build system .pro change sneaks in between the merge and the 
> >> enabling of enforcing CMake Coin, all dev integrations will fail for a 
> >> bit. I'll fix that up.
> >>
> >> But afterwards, regeneration of the CMake projects will be the 
> >> responsibility of the person changing the .pro / .pri / .qrc / 
> >> configure.json file.
> >> If you don't know how to do that, you can come to freenode #qt-cmake for 
> >> help.
> >>
> >>
> >> Just in case:
> >>
> >> README is at: https://github.com/qt/qtbase/tree/wip/cmake/cmake
> >> Guide is at: https://wiki.qt.io/CMake_Port/Porting_Guide
> >>
> >>
> >> Regards,
> >>
> >> Alexandru.
> >>
> >>> On 3. Feb 2020, at 14:52, Alexandru Croitor <alexandru.croi...@qt.io> 
> >>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> The Qt CMake Port team would like to merge the wip/cmake branch of qtbase 
> >>> to dev, soon™ (this week or next week).
> >>>
> >>> This is mostly a heads up email, so that it doesn't come as a total 
> >>> surprise.
> >>>
> >>> How this affects people:
> >>>
> >>> 1) The qmake Coin builds are still there and continue to work.
> >>>
> >>> 2) Soon after the merge, a qt5.git change will land which will add a few 
> >>> more qtbase Coin configurations which will build qtbase with CMake.
> >>>
> >>> 3) If these CMake Coin builds fail, developers of the respective changes 
> >>> will have to adapt their changes to fix the CMake builds.
> >>>
> >>> 3.1) Most of these fixes can probably be done automatically by running 
> >>> the magical pro2cmake.py script on the build system parts you changed.
> >>>
> >>> 4) The CMake port in not yet complete.
> >>>
> >>> 4.1) Not all tests are passing the test phase yet, that's why Coin 
> >>> ignores test phase errors and will always say that test phase passed 
> >>> successfully. The important part is that tests *build* successfully.
> >>>
> >>>
> >>> Preliminary tests showed that nothing breaks in Coin as a result of the 
> >>> merge.
> >>>
> >>>
> >>> The current merge diff is at:
> >>> https://codereview.qt-project.org/c/qt/qtbase/+/282101
> >>>
> >>> README is at: https://github.com/qt/qtbase/tree/wip/cmake/cmake
> >>> Guide is at: https://wiki.qt.io/CMake_Port/Porting_Guide
> >>>
> >>> Regards,
> >>> Alexandru.
> >>
> >> _______________________________________________
> >> Development mailing list
> >> Development@qt-project.org
> >> https://lists.qt-project.org/listinfo/development
> >
>
> _______________________________________________
> Development mailing list
> Development@qt-project.org
> https://lists.qt-project.org/listinfo/development
_______________________________________________
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Reply via email to