Re: [Development] Proposing to move deploy tools to qtbase

On 11/16/21 12:06 PM, EXT Craig Scott wrote: [proposal to move macdeployqt and windeployqt to qtbase] Both macdeployqt and windeployqt are small and don’t depend on anything other that QtCore (their tests do depend on QtTest as well). With feature freeze for 6.3 only a few weeks away, it woul

Re: [Development] Documentation of new Qt features in qtdoc

On Tue, 23 Nov 2021 at 09:39, EXT Craig Scott wrote: > > Thought I’d share how CMake’s release process handles this, for comparison. > > If a change introduces a new feature or a significant behavior change, we > have a dedicated directory in the repo (Help/release/dev >

Re: [Development] Documentation of new Qt features in qtdoc

On 23 Nov 2021, at 6:07 am, Edward Welbourne mailto:edward.welbou...@qt.io>> wrote: On Mon, Nov 22, 2021 at 10:43:45AM +, Edward Welbourne wrote: Documenting it while it's fresh in your mind generally leads to a better description, after all, Oswald Buddenhagen (22 November 2021 12:47) rep

Re: [Development] Documentation of new Qt features in qtdoc

On Mon, Nov 22, 2021 at 10:43:45AM +, Edward Welbourne wrote: >>> Documenting it while it's fresh in your mind generally leads to a >>> better description, after all, Oswald Buddenhagen (22 November 2021 12:47) replied: >> i'm not so sure about that. as seen by the quality of the [ChangeLog] >

Re: [Development] "error: ran out of registers during register allocation" when building qlibrary.cpp on macOS 11.6 with Clang 13

On Monday, 22 November 2021 05:47:04 PST Mitch Curtis wrote: > error: ran out of registers during register allocation Unless it's complaining about inline assembly, I don't see how this could be our fault. I don't see any inline assembly in qlibrary.cpp or in headers it includes, so my guess is

Re: [Development] Documentation of new Qt features in qtdoc

ChangeLog entries from the git log may often be badly-worded or be written badly for the audience that’s going to read them, but I think we should still start from those, for the sake of completeness. We can simply modify the tooling to output qdoc syntax instead of markdown. Then we'll end up

[Development] "error: ran out of registers during register allocation" when building qlibrary.cpp on macOS 11.6 with Clang 13

I'm running into the following error on macOS 11.6 with Clang 13: [577/1574] Building CXX object src/corelib/CMakeFiles/Core.dir/plugin/qlibrary.cpp.o FAILED: src/corelib/CMakeFiles/Core.dir/plugin/qlibrary.cpp.o /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/b

Re: [Development] Documentation of new Qt features in qtdoc

On Mon, Nov 22, 2021 at 10:43:45AM +, Edward Welbourne wrote: Documenting it while it's fresh in your mind generally leads to a better description, after all, i'm not so sure about that. as seen by the quality of the [ChangeLog] entries (in as far as present at all), many people have proble

Re: [Development] Documentation of new Qt features in qtdoc

On Fri, Nov 19, 2021 at 03:11:57PM +, Kai Koehne wrote: >>> Can we agree to document new features in Qt 6.3 and following >>> released directly in qtdoc.git? On 20 Nov 2021, at 01:12, Oswald Buddenhagen wrote: >> won't this cause conflict hell during release finalization? the >> turnaround ti