|
| 1 | +# Windows Platform Support |
| 2 | + |
| 3 | +## Current Status (2025-11-12) |
| 4 | + |
| 5 | +| Component | Linux | macOS | Windows | Notes | |
| 6 | +|-----------|-------|-------|---------|-------| |
| 7 | +| **WASI SDK** | ✅ | ✅ | ✅ | Full support with .exe extensions | |
| 8 | +| **C/C++ Components** | ✅ | ✅ | ✅ | All toolchain binaries work correctly | |
| 9 | +| **TinyGo** | ✅ | ✅ | ✅ | Cross-platform compatibility verified | |
| 10 | +| **Rust wasm32-wasip2** | ✅ | ✅ | ❌ | Blocked by missing wasm-component-ld.exe | |
| 11 | +| **JavaScript** | ✅ | ✅ | ✅ | Node.js and jco work on Windows | |
| 12 | +| **WASM Tools** | ✅ | ✅ | ✅ | All validation and composition tools work | |
| 13 | + |
| 14 | +## Known Limitation: Rust wasm32-wasip2 on Windows |
| 15 | + |
| 16 | +### The Issue |
| 17 | + |
| 18 | +Windows builds of Rust wasm32-wasip2 components fail with: |
| 19 | + |
| 20 | +``` |
| 21 | +error: linker `wasm-component-ld.exe` not found |
| 22 | + | |
| 23 | + = note: program not found |
| 24 | +``` |
| 25 | + |
| 26 | +### Root Cause |
| 27 | + |
| 28 | +The `wasm-component-ld` linker is required for the wasm32-wasip2 target. This tool: |
| 29 | +- Wraps `wasm-ld` (LLVM's WASM linker) |
| 30 | +- Converts core WASM modules to WASM components |
| 31 | +- Is distributed as part of the Rust compiler toolchain |
| 32 | + |
| 33 | +**Problem**: The Windows rustc distribution does not include `wasm-component-ld.exe`, or it's not in the expected PATH. |
| 34 | + |
| 35 | +### What We Fixed |
| 36 | + |
| 37 | +The rules_wasm_component codebase now correctly handles Windows: |
| 38 | + |
| 39 | +1. **WASI SDK binaries** - All tool paths include `.exe` extension on Windows (commit 471b2a8, e137324, 44887aa) |
| 40 | +2. **Platform detection** - Transitions detect Windows execution platform correctly |
| 41 | +3. **Linker configuration** - Adds `.exe` extension to wasm-component-ld on Windows (commit cef738e) |
| 42 | + |
| 43 | +The infrastructure works - the Rust toolchain just doesn't provide the required binary yet. |
| 44 | + |
| 45 | +### Evidence from CI |
| 46 | + |
| 47 | +The wasm32-wasip2 standard library IS installed: |
| 48 | +``` |
| 49 | +rust-std-1.90.0-wasm32-wasip2.tar.xz |
| 50 | +``` |
| 51 | + |
| 52 | +But the linker tool is missing: |
| 53 | +``` |
| 54 | +ERROR: Compiling Rust cdylib hello_component_wasm_lib_release_wasm_base (1 files) failed |
| 55 | +error: linker `wasm-component-ld.exe` not found |
| 56 | +``` |
| 57 | + |
| 58 | +### Workarounds |
| 59 | + |
| 60 | +**Option 1: Use wasm32-wasip1 (Older WASI Preview 1)** |
| 61 | +```python |
| 62 | +# In platforms/BUILD.bazel, use wasip1 instead of wasip2 |
| 63 | +platform( |
| 64 | + name = "wasm32-wasi", |
| 65 | + constraint_values = [ |
| 66 | + "@platforms//cpu:wasm32", |
| 67 | + "@platforms//os:wasi", |
| 68 | + "@rules_rust//rust/platform:wasi_preview_1", # Use Preview 1 |
| 69 | + ], |
| 70 | +) |
| 71 | +``` |
| 72 | + |
| 73 | +**Option 2: Build wasm-component-ld Manually** |
| 74 | +```bash |
| 75 | +# Clone Rust repository |
| 76 | +git clone https://github.com/rust-lang/rust.git |
| 77 | +cd rust |
| 78 | + |
| 79 | +# Build the linker tool |
| 80 | +cargo build --release -p wasm-component-ld |
| 81 | + |
| 82 | +# Add to PATH |
| 83 | +copy target\release\wasm-component-ld.exe %USERPROFILE%\.cargo\bin\ |
| 84 | +``` |
| 85 | + |
| 86 | +**Option 3: Wait for Rust Ecosystem** |
| 87 | + |
| 88 | +Track these Rust issues: |
| 89 | +- Rust Windows wasm32-wasip2 support maturity |
| 90 | +- wasm-component-ld distribution in rustup |
| 91 | + |
| 92 | +### Future Resolution |
| 93 | + |
| 94 | +This will be resolved when: |
| 95 | +1. Rust officially distributes `wasm-component-ld.exe` with Windows rustc |
| 96 | +2. Or rustup includes it when installing the wasm32-wasip2 target |
| 97 | +3. Or Bazel rules_rust provides a hermetic wasm-component-ld for Windows |
| 98 | + |
| 99 | +## Testing on Windows |
| 100 | + |
| 101 | +### What Works |
| 102 | + |
| 103 | +```bash |
| 104 | +# C/C++ WASM components |
| 105 | +bazel build //examples/cpp_component:... |
| 106 | + |
| 107 | +# JavaScript components |
| 108 | +bazel build //examples/js_component:... |
| 109 | + |
| 110 | +# TinyGo components |
| 111 | +bazel build //examples/tinygo:... |
| 112 | + |
| 113 | +# WASM composition and validation |
| 114 | +bazel test //tests/composition:... |
| 115 | +``` |
| 116 | + |
| 117 | +### What Doesn't Work |
| 118 | + |
| 119 | +```bash |
| 120 | +# Rust wasm32-wasip2 components |
| 121 | +bazel build //examples/basic:hello_component_release |
| 122 | +# ERROR: linker `wasm-component-ld.exe` not found |
| 123 | +``` |
| 124 | + |
| 125 | +## Commits and Progress |
| 126 | + |
| 127 | +| Commit | Description | Status | |
| 128 | +|--------|-------------|--------| |
| 129 | +| 471b2a8 | WASI SDK Windows .exe extension support | ✅ Complete | |
| 130 | +| e137324 | CC toolchain .exe paths | ✅ Complete | |
| 131 | +| 44887aa | String replacement fix for format errors | ✅ Complete | |
| 132 | +| b6b1b15 | Initial Windows linker detection in select() | ⚠️ Didn't work (wrong context) | |
| 133 | +| 8df9edb | Move detection to transition | ⚠️ Wrong settings path | |
| 134 | +| cef738e | Use correct rules_rust settings path | ✅ Works (but tool missing) | |
| 135 | + |
| 136 | +## Recommendation |
| 137 | + |
| 138 | +**For production use**: Document that Windows Rust wasm32-wasip2 support is experimental/unsupported until the Rust ecosystem provides the required tooling. |
| 139 | + |
| 140 | +**For contributors**: All Windows compatibility work is complete on the rules_wasm_component side. The blocker is upstream in Rust's Windows distribution. |
| 141 | + |
| 142 | +**For users**: Use Linux or macOS for Rust WASM component development, or use wasm32-wasip1 (Preview 1) on Windows as a temporary workaround. |
0 commit comments