Fix incorrect platform detection in setenvvar.bat on VS2022 #8866
+6
−5
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 pull request fixes incorrect platform detection in
setenvvar.batwhenbuilding Firebird on modern Visual Studio environments (VS2022 Build Tools).
The current script relies on
PROCESSOR_ARCHITECTURE, which always reportsAMD64even when using the x86 Native Tools Command Prompt. As a result,FB_TARGET_PLATFORMis always set tox64, and Win32 builds do not behavecorrectly.
This patch replaces the detection logic with the
%Platform%variable, whichcorrectly reports
x86orx64depending on the toolchain.Fixes #8865