Elgato_dark/rustdesk
1
0
Fork 0
mirror of https://github.com/rustdesk/rustdesk synced 2026-04-21 13:27:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Fix Markdown typo in BUILDING.md.

Browse source 
Co-authored-by: Jubilee <workingjubilee@gmail.com>
This commit is contained in:
Jonathan Gilbert 2026-02-02 16:57:53 -06:00 committed by GitHub
parent d78fb7d4c0
commit 213f03d13b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
BUILDING.md
View file

@ -238,7 +238,7 @@ RustDesk is undeniably complicated to build, with lots of moving parts. There ar
1. The build of the Rust core crate underlying RustDesk is done using Cargo. The exact parameters to Cargo are important. The `build.py` script does the correct builds in sequence. At a minimum, the `--flutter` flag must be passed into `build.py`; without it, the resulting `librustdesk.dll` lacks the numerous exported functions that the Flutter front-end relies upon.
- Windows: The build processes underlying Rust crate compilation will require that the Visual C++ build tools be available in the ambient environment. Run these commands from a `Developer Command Prompt for Visual Studio`, or explicitly run `vsvars.
- Windows: The build processes underlying Rust crate compilation will require that the Visual C++ build tools be available in the ambient environment. Run these commands from a `Developer Command Prompt for Visual Studio`, or explicitly run `vsvars`.
- The output from the build is placed into a subdirectory of `target` named after the build profile -- `debug` or `release`. Note that Rust builds can consume a very large amount of disk space. As of this writing, a build output folder in `target` may require 40GB or more of disk space for a full build.