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
Testing the automatic qmlls CMake type registration
First of all, setup qmlls in your favorite editor (see https://www.qt.io/blog/whats-new-in-qml-language-server-qmlls-shipped-with-qt-6.6 for instructions).
Steps
Scenario 1: automatic update of the linting suggestions
- Open the manual test using the
CMakeLists.txt(for QtC, for example) or the folder in which theCMakeLists.txtlies (for VS Code, for example) in the editor prepared for qmlls. - Make sure the project is configured and built.
- In your editor, open the
Main.qmlandhelloworld.h. - Modify the
helloworld.hfile by commenting the existingQ_PROPERTY myPPPout and savehelloworld.h. - Wait for the Main.qml file to automatically update its diagnostic to show
Could not find property "myPPP". It should also not propose myPPP as autocompletion inHelloWorldanymore. - Repeat steps 4 + 5 with your own modifications and check that the modification in the
helloworld.hcan be seen in theMain.qmlfile, without having to rebuild the project yourself.
Scenario 2: non-blocking completion
- Open the manual test using the
CMakeLists.txt(for QtC, for example) or the folder in which theCMakeLists.txtlies (for VS Code, for example) in the editor prepared for qmlls. - Make sure the project is configured and built.
- In your editor, open the
Main.qmlandhelloworld.h. - Modify the
helloworld.hfile by commenting the existingQ_PROPERTY myPPPout and savehelloworld.h. - Remove
myPPP: 55fromMain.qmland replace it withmyP: it should get autocompleted tomyPPP, without waiting for the CMake build process to finish.
Scenario 3: Automatic CMake build on WS opening
- Open the manual test using the
CMakeLists.txt(for QtC, for example) or the folder in which theCMakeLists.txtlies (for VS Code, for example) in the editor where qmlls is disabled. - Make sure the project build folder is configured and cleaned.
- Enable qmlls in your editor, and open
Main.qml - You should see lots of linting warnings about the missing qmltypes files of the AutoGenCMake module.
- After few seconds, qmlls should have built the project in the background, and retriggered a new linting pass, without any user interaction. The warnings about the missing qmltypes file of the AutoGenCMake module should disappear by themselves. Also make sure that qmlls didn't crash while doing that.