worker: build fastchess with build=release for static linking on Windows #2411
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
Member
|
i don't understand this.. the environment you compile fastchess in, is also the one supposed to execute it.. there's no need for static linking |
Collaborator
|
msys2 ucrt64 builds an application that needs:
If fastchess.exe does not find the 3 msys2 ucrt64 libraries, neither python3.exe, g++.exe, stockfish.exe should find their required libraries. |
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.
Build fastchess with
build=releaseto ensure static linking on Windows.Without this, the binary depends on MSYS64 UCRT DLLs, causing
nanosleep64entry point errors orEngine didn't respond to uciokfailures when run outside MSYS64.Related: Disservin/fastchess#950