Dario Gabriel LipicarandClaude Opus 4.8 8ed5e76ea5 feat(universal): route core universal modules through the cdylib mechanism
apiStyle for `interface: "universal"` core modules becomes "lp" (was "std"):
they now build as header-first cdylibs — Qt-free impl + the common
module-impl C ABI export seam + uniform Qt glue, with outbound
modules().<dep> calls hitting logos-protocol's lp_* C ABI directly. An
unchanged universal module recompiles Qt-free in its impl/wrapper TUs and
still loads via the same Qt plugin (load + call ABI preserved).

UI universal backends (type: ui_qml) derive a Qt SimpleSource and cannot be
Qt-free, so they stay on the std surface. Everything else (legacy) stays qt.

Pairs with logos-module-builder modulePreConfigure.universalCodegen, which
now derives the LIDL from the impl header and runs the cdylib backend.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-14 00:53:02 -03:00
2026-05-07 12:36:58 -03:00
2026-03-28 10:01:59 -04:00

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.

S
Description
Qt-specific plugin build logic
Readme
594 KiB
Languages
Nix 49.6%
C++ 45%
CMake 3.3%
Shell 1.4%
C 0.7%