mirror of
https://github.com/logos-co/logos-plugin-qt.git
synced 2026-08-27 08:51:07 +00:00
Dario Gabriel LipicarandClaude Opus 5
37b74d82ed
The guard test failed 11 assertions on Linux CI while passing on macOS. The
stubs never ran:
/build/work/bin-recorder/logos-cpp-generator:
/usr/bin/env: bad interpreter: No such file or directory
Error: logos-cpp-generator failed (exit status 126).
The nix build sandbox on Linux has no /usr/bin/env, so every stub exited 126
before recording anything, and the guard under test then reported a generator
failure -- a TRUE statement about a broken stub. The feature was working; the
fixture was not.
Stub shebang now points at ${pkgs.bash}/bin/bash (pkgs.bash is already in
nativeBuildInputs). lib/generate-module-headers.sh keeps its env shebang and
is unaffected: both this test and lib/buildHeaders.nix:98 invoke it as
`bash ${script}`, so its shebang is never used.
VERIFICATION IS INCOMPLETE, deliberately stated. The test passes on this
machine BOTH with and without the fix -- macOS's sandbox has /usr/bin/env, so
the negative control could not reproduce the failure and my local green proves
nothing. Docker was unavailable for a Linux run. The evidence for the fix is
the CI log naming the exact interpreter error, plus the mechanism being
unambiguous; Linux CI is the actual check.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
logos-plugin-qt
The Qt-specific build logic (CMake module, plugin compilation, header generation) as a standalone backend that logos-module-builder delegates to.
This enables swapping the plugin technology without changing the module builder or individual modules.