Make cross compiling the project using msvc-wine on Linux possible #4332
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Running win-build.bat inside Wine would be impractical, since the msbuild wrapper script shipped by msvc-wine cannot properly set up the environment variables if invoked from within Wine.
Contributor
|
Congrats on the initiative! |
botder
approved these changes
Aug 3, 2025
botder
added
enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to streamline compiling (mainly the Client) on Linux using msvc-wine. I plan on submitting a full write-up about the process to the wiki.
This PR replaces CertUtil with 7za.exe inside
utils/buildactions/utils.lua. This is needed, because Wine (as of writing) doesn't implement CertUtil, henceos.sha256_filewould fail otherwise. On Windows, this shouldn't break anything.The PR also introduces a helper build script
./wine-build.sh../win-build.batcan't be used, since themsbuildwrapper script that's shipped by msvc-wine fails to correctly set the paths in the environment variables if it's invoked from withing Wine. Also,vswhere.exewould just never work on Wine. This script is not strictly necessary for things to work though, as the individual commands can be invoked directly:Thus it can be removed from this PR, if requested.