rustdesk / rustdesk/rustdesk-server
rustdesk-server Compilation issues
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
I modified the cargo.toml file in the libs/hbc_common directory to enable the forwarding component to support using the Quic protocol connection. The modified content is as follows:
[features]
default = ["quic"]
quic = ["quinn"]
flatpak = []
After modification, proceed with cargo build release for compilation. Prompt during compilation
Describe the environment
- Windows 11 21H2 （64bit）
- rustup-init.exe
- VS2017/VS2019 is installed on the computer
How to Reproduce the bug
Expected behavior
I noticed that there is support for Quic code in Rustdesk's code, and I would like to test the effectiveness of Quic transmission. I ran the binary compiled on Rustdesk Github directly, but I feel the effect is not ideal
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with libs/hbc_common/Cargo.toml and the reported feature changes, then run cargo build --release on the stated Windows environment to capture the compilation failure shown in the issue. Compare the build result with the intended quic feature configuration; done means the project builds successfully with that configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100