Skip to content

docs: update Windows LLVM setup#299

Merged
hydai merged 1 commit into
mainfrom
docs/update-windows-llvm-setup
Jun 11, 2026
Merged

docs: update Windows LLVM setup#299
hydai merged 1 commit into
mainfrom
docs/update-windows-llvm-setup

Conversation

@hydai

@hydai hydai commented Jun 11, 2026

Copy link
Copy Markdown
Member

Explanation

This PR updates the Windows source-build instructions to match the current WasmEdge Windows CI setup. The previous page still pointed users at the older LLVM 16.0.6 Windows package and documented a manual Visual Studio Enterprise-to-Community path edit for diaguids.lib in LLVMExports.cmake.

The current CI uses the WasmEdge llvm-windows 21.1.3 package. I also verified the downloaded 21.1.3 asset locally and confirmed its exported CMake metadata no longer contains a hard-coded Visual Studio Enterprise/Community DIA SDK path.

Related issue

Fixes WasmEdge/WasmEdge#2423.

What type of PR is this

/kind documentation

Proposed Changes

  • Update the Windows build instructions to LLVM 21.1.3 and Windows SDK 26100.
  • Remove the obsolete manual LLVMExports.cmake workaround.
  • Use Invoke-WebRequest in the localized PowerShell download example.

This contribution was developed with assistance from OpenAI Codex.

Validation

  • git diff --check
  • npx prettier --check docs/contribute/source/os/windows.md i18n/zh/docusaurus-plugin-content-docs/current/contribute/source/os/windows.md
  • npm run build

Assisted-by: OpenAI Codex
Signed-off-by: hydai <z54981220@gmail.com>
@hydai hydai requested review from alabulei1 and juntao as code owners June 11, 2026 08:47
@hydai hydai requested review from 0yi0, dm4 and q82419 June 11, 2026 08:49
@hydai hydai merged commit cdfce6e into main Jun 11, 2026
6 checks passed
@hydai hydai deleted the docs/update-windows-llvm-setup branch June 11, 2026 08:53
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.

Windows build instructions expect VS Enterprise

2 participants