Skip to content

ci: switch to mcpp build (.xlings.json pins mcpp 0.0.3)#11

Merged
Sunrisepeak merged 1 commit intomainfrom
ci/mcpp-build
May 9, 2026
Merged

ci: switch to mcpp build (.xlings.json pins mcpp 0.0.3)#11
Sunrisepeak merged 1 commit intomainfrom
ci/mcpp-build

Conversation

@Sunrisepeak
Copy link
Copy Markdown
Member

Replace multi-platform xmake CI with a mcpp-driven Linux build. .xlings.json pins mcpp = { linux = "0.0.3" }; CI runs xlings install -y + mcpp build. mcpp test is intentionally not invoked since llmapi's integration tests need API keys; xmake.lua keeps the local test path. The pre-existing xmake CI was failing on main for environment-related reasons (xlings v0.4.0 elfpatch breakage), this fixes that.

Replaces the multi-platform xmake CI with a single mcpp-driven
Linux job (`mcpp build`):
- `.xlings.json` declares `mcpp = { linux = "0.0.3" }`. The previous
  xmake/cmake/ninja/gcc/llvm pins are no longer relevant for CI;
  mcpp 0.0.3 ships its own toolchain via xlings.
- `.github/workflows/ci.yml` boots xlings, runs `xlings install -y`,
  then `mcpp build` against the existing mcpp.toml.

`mcpp test` is intentionally not run here — llmapi's tests need
network credentials (OpenAI / Anthropic API keys) so they don't
belong in a public CI Linux job. xmake.lua stays for local
development with the integration tests.
@Sunrisepeak Sunrisepeak merged commit 02e3765 into main May 9, 2026
1 check passed
@Sunrisepeak Sunrisepeak deleted the ci/mcpp-build branch May 9, 2026 20:13
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.

1 participant