Skip to content

Fix C++ module usage - #421

Merged
RobLoach merged 8 commits into
masterfrom
fix-cpp-modules
Jul 30, 2026
Merged

Fix C++ module usage#421
RobLoach merged 8 commits into
masterfrom
fix-cpp-modules

Conversation

@RobLoach

Copy link
Copy Markdown
Owner

Fixes #420

Consuming raylib_cpp_modules failed with "the compiler does not provide a way to discover the import graph dependencies" because C++ module scanning requires a Ninja/Visual Studio generator and a scan-capable compiler, which wasn't checked or documented, and the module path had no test.

  • Harden modules/CMakeLists.txt: warn with an actionable message when the generator can't scan for modules, and clean up the target setup.
  • Add an import raylib; example built only when modules are enabled.
  • Add a CI job that builds the modules with Ninja + Clang so it stays working.
  • Document module requirements and a FetchContent consumer template in the README.

Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread modules/CMakeLists.txt Outdated
Comment thread README.md Outdated
@RobLoach
RobLoach merged commit d502e0d into master Jul 30, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Trying out raylib modules on my macos - "compiler does not provide a way to discover the import graph"

1 participant