Meta: Refactor the way the GUI framework is picked

This is largely based of off the work done by Andrew Kaster in #5918.
Having this toggle makes much more sense, especially if there will be
more UIs in the future.

Co-authored-by: Andrew Kaster <andrew@ladybird.org>
This commit is contained in:
Undefine
2026-03-27 21:03:22 +01:00
committed by Andrew Kaster
parent 4eda70a4f1
commit fbbcc73fea
Notes: github-actions[bot] 2026-03-29 20:01:42 +00:00
8 changed files with 23 additions and 28 deletions

View File

@@ -254,16 +254,14 @@ Ladybird will be built with one of the following browser frontends, depending on
* [Qt](https://doc.qt.io/qt-6/) - The UI used on all other platforms.
* [Android UI](https://developer.android.com/develop/ui) - The native UI on Android.
The Qt UI is available on platforms where it is not the default as well (except on Android). To build the
Qt UI, install the Qt dependencies for your platform, and enable the Qt UI via CMake:
The Qt UI is available on platforms where it is not the default as well (except on Android).
You can pick the UI using the `LADYBIRD_GUI_FRAMEWORK` option, for example to enable the Qt UI:
```bash
# From /path/to/ladybird
cmake --preset default -DENABLE_QT=ON
cmake --preset default -DLADYBIRD_GUI_FRAMEWORK=Qt
```
To re-disable the Qt UI, run the above command with `-DENABLE_QT=OFF`.
### Build error messages you may encounter
The section lists out some particular error messages you may run into, and explains how to deal with them.