Sergey CherepanoffandJohn Tur
769a8a650e
### Summary This PR changes `gpui/build.rs` to look up the Windows SDK directory in the registry instead of falling back to a hard-coded path. --- ### Problem Currently, building `gpui` on Windows requires `fxc.exe` to be in `PATH` or at a predefined location (unless `GPUI_FXC_PATH` is set). This requires to maintain a certain build environment with proper paths/vars or to install the specific SDK version. It is possible to find the SDK automatically using the registry keys it creates upon installation. Specifically in `SOFTWARE\\WOW6432Node\\Microsoft\\Microsoft SDKs\\Windows\\v10.0` branch there are: * `InstallationFolder` telling the SDK installation location; * `ProductVersion` telling the SDK version in use. These keys provide enough information to locate the SDK binaries, with added robustness: * handles non-standard SDK installation path; * deterministically selects the latest SDK when multiple versions are present. --- ### Changes Made * **Updated `crates/gpui/build.rs`**: * added dependency on `winreg` * introduced `find_latest_windows_sdk_binary()` helper * updated fallback logic to use registry lookup This PR only changes the fallback location, and does not touch the established environment-based workflow. Release Notes: - N/A --- ### Impact Reduces manual configuration needed to build GPUI on Windows. --------- Co-authored-by: John Tur <john-tur@outlook.com>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.