vasilito
f31522130f
Build system (5 gaps hardened): - COOKBOOK_OFFLINE defaults to true (fork-mode) - normalize_patch handles diff -ruN format - New 'repo validate-patches' command (25/25 relibc patches) - 14 patched Qt/Wayland/display recipes added to protected list - relibc archive regenerated with current patch chain Boot fixes (fixable): - Full ISO EFI partition: 16 MiB → 1 MiB (matches mini, BIOS hardcoded 2 MiB offset) - D-Bus system bus: absolute /usr/bin/dbus-daemon path (was skipped) - redbear-sessiond: absolute /usr/bin/redbear-sessiond path (was skipped) - daemon framework: silenced spurious INIT_NOTIFY warnings for oneshot_async services (P0-daemon-silence-init-notify.patch) - udev-shim: demoted INIT_NOTIFY warning to INFO (expected for oneshot_async) - relibc: comprehensive named semaphores (sem_open/close/unlink) replacing upstream todo!() stubs - greeterd: Wayland socket timeout 15s → 30s (compositor DRM wait) - greeter-ui: built and linked (header guard unification, sem_compat stubs removed) - mc: un-ignored in both configs, fixed glib/libiconv/pcre2 transitive deps - greeter config: removed stale keymapd dependency from display/greeter services - prefix toolchain: relibc headers synced, _RELIBC_STDLIB_H guard unified Unfixable (diagnosed, upstream): - i2c-hidd: abort on no-I2C-hardware (QEMU) — process::exit → relibc abort - kded6/greeter-ui: page fault 0x8 — Qt library null deref - Thread panics fd != -1 — Rust std library on Redox - DHCP timeout / eth0 MAC — QEMU user-mode networking - hwrngd/thermald — no hardware RNG/thermal in VM - live preload allocation — BIOS memory fragmentation, continues on demand
65 lines
1.9 KiB
Plaintext
65 lines
1.9 KiB
Plaintext
// Copyright (C) 2022 The Qt Company Ltd.
|
|
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
|
|
|
|
//! [using qt module]
|
|
|
|
\section1 Using the Module
|
|
|
|
Using a Qt module requires linking against the module library, either
|
|
directly or through other dependencies. Several build tools have dedicated
|
|
support for this, including \l{CMake Documentation}{CMake} and
|
|
\l{qmake}.
|
|
|
|
\section2 Building with CMake
|
|
|
|
Use the \c{find_package()} command to locate the needed module components in
|
|
the \c{Qt6} package:
|
|
|
|
//! [using qt module]
|
|
|
|
//! [using the c++ api]
|
|
Using a Qt module's C++ API requires linking against the module library,
|
|
either directly or through other dependencies. Several build tools have
|
|
dedicated support for this, including \l{CMake Documentation}{CMake} and
|
|
\l{qmake}.
|
|
//! [using the c++ api]
|
|
|
|
//! [using the qml api]
|
|
The QML types of the module are available through the \c \1 import. To use
|
|
the types, add the following import statement to your .qml file:
|
|
|
|
\qml
|
|
import \1
|
|
\endqml
|
|
//! [using the qml api]
|
|
|
|
//! [building with qmake]
|
|
|
|
\section2 Building with qmake
|
|
|
|
To configure the module for building with qmake, add the module as a value
|
|
of the \c QT variable in the project's .pro file:
|
|
|
|
//! [building with qmake]
|
|
|
|
//! [building_with_qmake]
|
|
To configure the module for building with qmake, add the module as a value
|
|
of the \c QT variable in the project's .pro file:
|
|
|
|
\code
|
|
QT += \1
|
|
\endcode
|
|
//! [building_with_qmake]
|
|
|
|
//! [building with cmake]
|
|
Use the \c {find_package()} command to locate the needed module component
|
|
in the \c {Qt6} package:
|
|
|
|
\code
|
|
find_package(Qt6 REQUIRED COMPONENTS \1)
|
|
target_link_libraries(mytarget PRIVATE Qt6::\1)
|
|
\endcode
|
|
|
|
For more details, see the \l {Build with CMake} overview.
|
|
//! [building with cmake]
|