vasilito
49326998a3
Round 1 of the 3D-Desktop-Implementation work. Closes audit §3.4 #1 (kirigami QtNetwork lie-grade stub) and the missing bin/ toolchain wrappers that block any meson regen of mesa-style recipes. kirigami Icon primitive network path - local/patches/kirigami/02-qnetwork-real-implementation.patch: replaces the upstream Kirigami's Icon::loadImageFromSource lie-grade 'qnam = nullptr /* Redox: networkAccessManager not available */' hardcode with a real 'qnam = new QNetworkAccessManager(this)' allocation. The parented QNetworkAccessManager is destroyed with the icon; the existing handleFinished falls through to the placeholder icon when scheme:network is unavailable, so the network path now actually works on Redox. - local/recipes/kde/kirigami/recipe.toml: wired the patch into [source].patches and added cookbook_apply_patches call. Removed the -I${COOKBOOK_SOURCE}/stubs/QtNetwork CMAKE_CXX_FLAGS entry that previously shadowed the real QtNetwork headers with the stub classes. Stub directory removal - local/recipes/kde/kirigami/source/stubs/QtNetwork/: 3 files deleted (QNetworkAccessManager returning nullptr, minimal Q_OBJECT-having QNetworkReply, forward-declared QNetworkRequest). The real QtNetwork (built via Qt6::Network in qtbase) is now used. - local/recipes/kde/sddm/stubs/: directory deleted entirely. The stubs/linux/{kd.h,vt.h} subdir was orphaned (SDDM patches wrap their use in #if !defined(__redox__) so the stubs were never compiled on Redox). After the linux/ subdir removal the stubs/ dir was empty. bin/ toolchain wrappers (required by the cookbook's [binaries] block at src/cook/script.rs:340; without these, meson --internal regenerate fails with 'x86_64-unknown-redox-gcc-ar: No such file or directory') - bin/x86_64-unknown-redox-gcc-ar - bin/x86_64-unknown-redox-gcc-ranlib - bin/x86_64-unknown-redox-g++ - bin/x86_64-unknown-redox-cpp All four are 5-line redbear-run-tool wrappers matching the pattern of the pre-existing x86_64-unknown-redox-{gcc,c++}. local/docs/3D-DESKTOP-COMPREHENSIVE-PLAN.md - §8.1 Implementation progress log added, recording this commit (Round 1) alongside the previously-committed Rounds 0-3 of the implementation work (commits0b19fddd2c,e6e4289113,86a162c803). §8.1 also documents the audit correction: the Mesa 'link never completed' is actually a mesa-config failure due to libclc.pc missing, not a link error. Recipe-level stub removal and bin/ toolchain wrappers address one blocker; libclc cook run remains the next Mesa prerequisite. Verified: PATH=.../bin:$PATH x86_64-unknown-redox-gcc-ar --version returns 'GNU ar (GNU Binutils) 2.43.1' via redbear-run-tool. No operator files (local/recipes/system/driver-manager/, the new NETWORKING-AND-DRIVERS-*-ASSESSMENT-2026-07-27.md docs, the libclc untracked source files) were touched in this commit.
6 lines
159 B
Bash
Executable File
6 lines
159 B
Bash
Executable File
#!/usr/bin/env bash
|
|
set -euo pipefail
|
|
|
|
script_dir="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)"
|
|
exec "${script_dir}/redbear-run-tool" "$(basename "$0")" "$@"
|