-
Notifications
You must be signed in to change notification settings - Fork 0
Docs: verify Windows/MSYS2 native build instructions #10
Copy link
Copy link
Open
Labels
buildConfigure, build, toolchain, and dependency setupConfigure, build, toolchain, and dependency setupdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomersvalidationTests, instrumentation, smoke routes, and regression toolingTests, instrumentation, smoke routes, and regression tooling
Description
Metadata
Metadata
Assignees
Labels
buildConfigure, build, toolchain, and dependency setupConfigure, build, toolchain, and dependency setupdocumentationImprovements or additions to documentationImprovements or additions to documentationgood first issueGood for newcomersGood for newcomersvalidationTests, instrumentation, smoke routes, and regression toolingTests, instrumentation, smoke routes, and regression tooling
Goal
Verify the Windows/MSYS2 native-port setup from a clean clone and update
docs/BUILDING.mdwith any missing package names, path notes, or troubleshooting details.Why this matters
Windows users will test this immediately after public launch. The current docs list the expected MSYS2 MINGW64 packages, but maintainer verification is still weaker than macOS/Linux.
Suggested steps
docs/BUILDING.md.baserom.u.z64or pass--romexplicitly.Acceptance criteria
docs/BUILDING.mdis updated with any corrected MSYS2 package names or setup caveats.Asset rule
Do not upload or commit ROMs, extracted assets, save files, or screenshots containing game imagery. Text logs are fine.