Let me publish here a text from Michael Weghorn's letter to our dev mailing list about current Qt6 plugin for Windows build status (because I like when more people can see such important information):
Earlier this year, initial support for the qt6 vcl plugin on Windows (and macOS) was implemented on master.
Below is a summary of the current status and potential next steps from my perspective.
I haven't used/tested it much myself beyond the point of "It starts and looks plausible at first" when contributing to it in the past and it is not my own main focus now. The below is meant as a basis for further discussion and coordinating efforts between those who are interested in getting involved to further improve it.
If you have any thoughts or are interested in getting involve, feedback is very welcome!
I think in particularly steps described in "Identify and address what else is missing" could be a good starting point for both, developers (already now, requires building from source), and non-developers (in
particular once tests builds for Windows including the qt6 vcl plugin are provided).
LibreOffice: qt6 vcl plugin on Windows
Background/Motivation
So-called "vcl plugins" are used in LibreOffice to implement the user interface and platform-specific aspects. They can either make use of third-party GUI toolkits or implement the low-level logic themselves.
The Qt-based vcl plugins that use the Qt UI toolkit were originally only used on Linux and similar Unix-based systems. qt5/qt6 was later also selected as the basis for the newly introduced WebAssembly port.
Reusing/Suppporting the qt6 vcl plugin on more platforms could be a potential approach to
- let an existing cross-platform UI toolkit take care of more platform-specific logic instead of "reinventing the wheel"
- unify and share more code across different platforms, also to reduce the maintenance effort
- reduce (but not eliminate) the need for Windows-specific code/knowledge
- ensure reliability and continued development/progress of the user interface (and more) on Windows despite most developers (currently) not working on Windows or Windows-specific code
- allow to make use of capabilities that Qt provides to allow theming/styling of the application
- get support for the newer UIA (User Interface Automation) accessibility protocol on Windows via Qt's internal accessibility bridge
- gain support for "native widgets" if combined with the "Qt welding" task (https://bugs.documentfoundation.org/show_bug.cgi?id=130857)
Since there is no real "standard native UI toolkit" on Windows (see e.g. also the discussion in
https://bugs.documentfoundation.org/show_bug.cgi?id=164656), no clear alternative candidate seems to be available to implement support for "native widgets" on Windows.
Current status
The qt6 vcl plugin code and related code was refactored to also allow building the qt6 vcl plugin on Windows and macOS.
Commit enabling build support on Windows:
https://git.libreoffice.org/core/commit/4d3a291b5d2d8a2dbdae5aca0d5fd506b5d5b0b9
Commit enabling build support on macOS:
https://git.libreoffice.org/core/commit/ddfc4058cfff09454621fe68f8804bbf289558b5
This work was inspired by/based on an earlier WIP branch …

gdb index cache status
If you have ideas for videos (or even better, can help us to make them), join the LibreOffice Marketing project: 
















