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
43 lines
1.4 KiB
Plaintext
43 lines
1.4 KiB
Plaintext
// Copyright (C) 2022 The Qt Company Ltd.
|
|
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
|
|
|
|
//! [cli-build-cmake]
|
|
|
|
\section1 Building and Running from the Command Line
|
|
|
|
To build an example application from the command line, create a build
|
|
directory for it. Switch to the build directory and run \c qt-cmake to
|
|
configure your project for building. If the project is configured
|
|
successfully, the generated files enable you to build the project.
|
|
|
|
\badcode
|
|
md <build_directory>
|
|
cd <build_directory>
|
|
<qt_installation_directory>\bin\qt-cmake -GNinja <source_directory>
|
|
<generator>
|
|
\endcode
|
|
|
|
The commands create an executable in the build directory. The \c CMake
|
|
tool reads the project file and produces instructions for how to build
|
|
the application. The generator then uses the instructions to produce
|
|
the executable binary.
|
|
|
|
For example, to build the Notepad example on Windows, when using Ninja
|
|
as the generator, enter the following commands:
|
|
|
|
\badcode \QtVersion
|
|
md notepad-build
|
|
cd notepad-build
|
|
C:\Qt\\1\msvc2022_64\bin\qt-cmake -GNinja C:\Examples\notepad
|
|
ninja
|
|
\endcode
|
|
|
|
If you do not use Ninja as the generator, use the generator-independent
|
|
CMake command to build the application instead of \c ninja:
|
|
|
|
\badcode
|
|
cmake --build
|
|
\endcode
|
|
|
|
//! [cli-build-cmake]
|