Fix VS2026 being passed an unsupported debug flag in -c fastbuild - #796
Open
robinlinden wants to merge 1 commit into
Open
Fix VS2026 being passed an unsupported debug flag in -c fastbuild#796robinlinden wants to merge 1 commit into
robinlinden wants to merge 1 commit into
Conversation
The `/DEBUG:FASTLINK` flag was removed in VS2026, so passing it leads to a warning.
LINK : warning LNK4315: /DEBUG:FASTLINK is no longer supported.
Using /DEBUG:FULL instead. Use a VS 2022 toolchain to continue
building with /DEBUG:FASTLINK
robinlinden
force-pushed
the
fix-vs2026-fastbuild-link-warning
branch
from
July 18, 2026 19:01
9736121 to
42bacf6
Compare
robinlinden
marked this pull request as ready for review
July 18, 2026 19:05
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.
The
/DEBUG:FASTLINKflag was removed in VS2026, so passing it leads to a warning.This is a bit of an issue since that warning is promoted to an error if you're using
--features=treat_warnings_as_errors.Fixes #558, #749