-
|
Heya We've been using RustDesk for a while now and couldn't be happier with its functionality, but a question has been burning for months now; why do custom clients have to be built on a shared build server? Why can I not do this on my own RustDesk server? |
Beta Was this translation helpful? Give feedback.
Replies: 0 comments 1 reply
-
|
Building software for multiple platforms is far from simple — it’s inherently complex and resource-intensive. For example:
These platform-specific requirements cannot be fully satisfied on a Linux server alone. As a result, you either need physical or virtual machines running Windows and macOS, or you rely on paid CI/CD services (GitHub Actions, Azure Pipelines, Bitrise, etc.) that provide hosted macOS and Windows runners. In short: cross-platform desktop distribution is painful and expensive by design, and there’s no way around it if you want officially signed, store-ready, or notarized binaries. |
Beta Was this translation helpful? Give feedback.
Building software for multiple platforms is far from simple — it’s inherently complex and resource-intensive.
For example:
To produce a proper Windows executable, you must build on Windows. This requires setting up a full development environment (Visual Studio, Windows SDK, build tools, etc.) and obtaining a valid code-signing certificate.
To produce a proper macOS (or iOS) executable, you must build on macOS. This again requires a complete separate toolchain (Xcode, command-line tools, etc.) and an Apple Developer account for notarization and signing.
These platform-specific requirements cannot be fully satisfied on a Linux server alone. As a result, you either need physical or vir…