Skip to content

[Part B] docs: build and run with xmake or with mcpp, and the two project templates - #10

Open
Sunrisepeak wants to merge 1 commit into
pr/mcpp-build-supportfrom
pr/docs-build-and-run
Open

[Part B] docs: build and run with xmake or with mcpp, and the two project templates#10
Sunrisepeak wants to merge 1 commit into
pr/mcpp-build-supportfrom
pr/docs-build-and-run

Conversation

@Sunrisepeak

@Sunrisepeak Sunrisepeak commented Sep 12, 2026

Copy link
Copy Markdown
Owner

Part B / 2(Part A:#11,mcpp 构建支持)。只有文档,没有代码;一个 commit。

内容

  • README.md 的「快速运行」拆成两块:先「用 mcpp」(Windows / Linux / macOS:mcpp run xrgui_hello--features examples --releasemcpp new myapp --template xrgui:hello),后「用 xmake」;两条链并存的说明作为 > 注: 放在这一节末尾。
  • 新增 docs/build-and-development.md:README 的文档表从一开始就链接到它,但仓库里一直没有这个文件。内容:两条构建链各自的环境要求、命令、生成资产的去向、目标与依赖对照、平台支持(三个平台一张表,macOS 行说明只对 Apple 生效的三处配置)、两个模板和消费者必须自己说的两件事(Linux 工具链、设备轴)、showcase 在 debug 构建下对 validation layer 的依赖、Windows 上 GUI 子系统的代价;文末链接 mcpp 仓库、文档、索引、插件仓库,以及 mcpp 仓库里给 AI 助手用的 skill 入口和一段可直接发给助手的提示。
  • PROJECT_INTRO.mdproperties/showcase/quick_start.mdlayout_doc.mdsrc.hello/main.cppsrc.examples/main.cpp 的引用,跟随 Part A 改到 templates/ 下。

对 xmake 的影响:无。

合并顺序:在 Part A 之后。base 就是 Part A 的分支,所以这里的 diff 只有文档,而 CI 跑在「A 加文档」的树上;A 合并后把 base 换回 master 即可。

@Sunrisepeak
Sunrisepeak changed the base branch from base/upstream-master to pr/mcpp-build-support September 12, 2026 19:12
@Sunrisepeak Sunrisepeak changed the title docs: build and run with xmake or with mcpp, and the two project templates [Part B] docs: build and run with xmake or with mcpp, and the two project templates Sep 12, 2026
@Sunrisepeak
Sunrisepeak force-pushed the pr/docs-build-and-run branch 2 times, most recently from 5a84e7a to 076bf57 Compare September 12, 2026 19:59
README's quick-run becomes two blocks, mcpp first (it covers three
platforms) and xmake second, closed by a note that the two chains build
the same tree. docs/build-and-development.md -- linked from the README's
table since the beginning but never present -- states what each chain
needs, the commands, where generated assets go, targets and
dependencies side by side, platform support including the three
Apple-only configurations, the two templates and what a template
project must say itself (toolchain, accelerator), the showcase's need
for the validation layer in a debug build, and the Windows GUI
subsystem's cost. Links to the mcpp repository, index, plugins and the
AI skill entry close it. Other pages follow the entry points to
templates/.
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