Qt6: update doc
This commit is contained in:
5 files changed
+36
-12
No files matched your search
@@ -60,6 +60,7 @@ If your platform needs specific lib/include paths for the client, you can use `L
|
||||
It's also possible to skip parts even if libraries are present in the compilation environment:
|
||||
|
||||
* `make client SKIPQT=1` to skip GUI even if Qt is present
|
||||
* `make client SKIPQT6=1` to skip Qt6 even if Qt6 is present, anf fallback on Qt5
|
||||
* `make client SKIPBT=1` to skip native Bluetooth support even if libbluetooth is present
|
||||
* `make client SKIPPYTHON=1` to skip embedded Python 3 interpreter even if libpython3 is present
|
||||
* `make client SKIPLUASYSTEM=1` to skip system Lua lib even if liblua5.2 is present, use embedded Lua lib instead
|
||||
@@ -86,6 +87,8 @@ One tool requires a CUDA compilation environment, it can be skipped as well:
|
||||
|
||||
Some unittests are available via `make check`, which is actually triggering individual targets as for `make install`.
|
||||
|
||||
* `SKIPUV=1 tools/pm3_tests.sh` to skip usage of `uv` even if `uv` is present, and force usage of `python3` (in which case you must take care of installing the script dependencies yourself)
|
||||
|
||||
`make install` is actually triggering the following individual targets which can be accessed individually:
|
||||
|
||||
* `make client/install`
|
||||
|
||||
Reference in new issue
Block a user