[Major Feature] Cross-compilation for Windows from Linux #162
Labels
No labels
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
priority:tier4-deferred
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:procgen
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#163 [Minor Feature] Packaging variants: light vs batteries-included
john/McRogueFace
Reference
john/McRogueFace#162
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Currently building Windows releases requires booting a Windows machine. This friction discourages frequent releases and slows iteration.
Goal
Enable cross-compilation from Linux to produce Windows executables, eliminating the need for a Windows development environment.
Approach Options
MinGW-w64 Cross Compiler
x86_64-w64-mingw32-g++toolchainDocker-based Windows Build
Zig as Cross-Compiler
zig cccan target Windows from LinuxDependencies to Cross-Compile
Success Criteria
make windowsfrom Linux produces working .exeNotes
The 7DRL 2025 release shipped both AppImage (Linux) and Windows zip, proving both targets work. The goal is just to build both from one environment.
Related
Summary of Windows cross-compilation fixes:
Key technical issues resolved: