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
61 lines
2.0 KiB
Plaintext
61 lines
2.0 KiB
Plaintext
// Copyright (C) 2025 The Qt Company Ltd.
|
|
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
|
|
|
|
/*!
|
|
\title <Application Example Name>
|
|
\ingroup <Group Name>
|
|
\example <path/to/example/dir>
|
|
\brief <Description of the example's objective in one sentence.>
|
|
\meta <{tag}{Appropriate tag to display in Qt Creator}>
|
|
\examplecategory {Application Examples}
|
|
\image {<examplename-screenshot>}{<alt text>}
|
|
|
|
<Explain the objective of the example:
|
|
Explain which Qt technologies are used,
|
|
Explain what Qt features are shown.>
|
|
|
|
<Optional - Use this section for more complicated examples.>
|
|
\image {<examplename-workflow-diagram>}{<alt text>}
|
|
|
|
\include examples-run.qdocinc
|
|
<Describe the expected application behavior after running the example.>
|
|
|
|
\section1 Platform notes
|
|
<Optional - Mention limitations of target platforms, if any.>
|
|
|
|
\section1 UI walkthrough
|
|
<Optional - Use this section for more complicated examples.>
|
|
|
|
<Describe how to navigate and access different parts of the example/UI.>
|
|
|
|
\setion1 Relevant modules and classes
|
|
<Optional - Use this section for more complicated examples.>
|
|
|
|
This example introduces the following Qt <modules/classes>:
|
|
<Link the relevant modules/classes>
|
|
|
|
\section2 Class Hierarchy
|
|
<Optional - Use this section for more complicated examples.>
|
|
|
|
\image {<examplename-class-hierarchy>}{<alt text>}
|
|
|
|
\section1 <Feature A>
|
|
<Explain the implementation of Feature A in the code.
|
|
Add the relevant code snippet.>
|
|
|
|
\section1 <Feature B>
|
|
<Explain the implementation of Feature B in the code.
|
|
Add the relevant code snippet.>
|
|
|
|
\section1 Best practices
|
|
<Optional>
|
|
|
|
<Include best practices related to the example if applicable.>
|
|
|
|
<Optional - use this section if the example was tested with Squish>
|
|
\include squish-tested-example.qdocinc
|
|
|
|
\section1 Source files
|
|
|
|
\sa {All Qt Examples}, <Link to other relevant docs.>
|