feat(ftxui): compile 7.0.3's own module units — import ftxui; works

Upstream's new C++20 module units (src/ftxui/*.cppm) join the sources, so
7.0.3 consumers can `import ftxui;` — they are global-fragment includes +
`using` re-exports, every declaration stays attached to the global module,
and `#include`/`import` mix freely against the same compiled objects. On
6.1.9 the .cppm globs are zero-hit warnings (redis-plus-plus union
precedent). A new CompatModule smoke test imports ftxui and renders.

Verified locally (mcpp 2026.8.29.1): `mcpp test -p core` passes on 7.0.3
(both #include and `import ftxui;` smoke tests) and on 6.1.9 (loop.cpp
kept, zero-hit .cppm globs are warnings); `mcpp xpkg parse` green.

Author: FarnaHerry

pkgs/c/compat.ftxui.lua

@@ -10,9 +10,11 @@
 -- component,util}), so the 6.1.9 globs apply verbatim, and the public header
 -- API this index's smoke test uses (hbox/text/separator, `Dimension::Fit`,
 -- `Screen::Create(Dimensions, Dimensions)`, `Render`) is source-compatible
--- with 6.1.9. Upstream added C++20 module units (src/ftxui/*.cppm,
--- FTXUI_BUILD_MODULES, off by default); the `*.cpp` globs never match them,
--- and the plain .cpp sources still compile header-only style.
+-- with 6.1.9. Upstream added C++20 module units (src/ftxui/*.cppm) and this
+-- descriptor compiles them, so 7.0.3 consumers can `import ftxui;` — the
+-- units are global-fragment includes + `using` re-exports, every declaration
+-- stays attached to the global module, and `#include`/`import` can be mixed
+-- in one consumer against the same compiled objects.
 --
 -- ONE version skew the globs cannot express (no per-version build blocks,
 -- mcpp-community/mcpp#290): FTXUI 7 moved Loop's method definitions from
@@ -96,6 +98,15 @@ package = {
             "*/src/ftxui/**/*.cpp",
             "!*/src/ftxui/**/*_test.cpp",      -- gtest files (30+ in 6.1.9, 47 in 7.0.3)
             "!*/src/ftxui/**/*_fuzzer.cpp",     -- fuzz targets (16 in 6.1.9, 6 in 7.0.3)
+            -- 7.0.3's own module units: global-fragment includes + `using`
+            -- re-exports, so `import ftxui;` works and still links against
+            -- the compiled .cpp objects. 6.1.9 has no .cppm — these globs
+            -- are zero-hit warnings there, same as the redis-plus-plus union.
+            "*/src/ftxui/screen.cppm",
+            "*/src/ftxui/dom.cppm",
+            "*/src/ftxui/component.cppm",
+            "*/src/ftxui/util.cppm",
+            "*/src/ftxui/ftxui.cppm",
         },
         targets = { ["ftxui"] = { kind = "lib" } },
         deps    = { },

tests/examples/core/tests/module.cpp

@@ -0,0 +1,19 @@
+// FTXUI 7 module smoke: compat.ftxui 7.0.3 compiles upstream's own .cppm
+// units, so consumers can `import ftxui;` instead of (or mixed with)
+// #include — the re-export style keeps every declaration in the global
+// module, so both spellings link against the same objects.
+import ftxui;
+
+#include <string>
+
+#include <gtest/gtest.h>
+
+TEST(CompatModule, FtxuiImport) {
+    using namespace ftxui;
+    Element document = hbox({text("module"), separator(), text("ftxui")});
+    Screen screen = Screen::Create(Dimension::Fit(document), Dimension::Fit(document));
+    Render(screen, document);
+    const std::string rendered = screen.ToString();
+    EXPECT_TRUE(rendered.find("module") != std::string::npos &&
+                rendered.find("ftxui") != std::string::npos);
+}