Skip to content

Making /Qspectre 'Required Libraries' section more clear #3237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 3, 2021

Conversation

ericbrumer
Copy link
Contributor

A C++ customer opened a DevCom ticket (https://developercommunity.visualstudio.com/t/Build-unexpectedly-succeeds-with-Qspect/1437998) indicating some confusion with what happens when the /Qspectre switch is thrown. The compiler switch only modifies the compiler, and our MSBuild properties for C++ projects is what links in the additional libraries.

This PR attempts to clear that up.

@v-andreaco v-andreaco requested a review from colin-home July 2, 2021 20:11
@v-andreaco v-andreaco added aq-pr-triaged Tracking label for the PR review team Change sent to author labels Jul 2, 2021
Update to distinguish command line and IDE behavior better.
Explicitly call for mitigated libraries in command-line builds. Provide some hand-wavy directions on how.
Clarify 2015 behavior and instructions.
@colin-home colin-home merged commit 4d3435a into MicrosoftDocs:master Jul 3, 2021
@colin-home
Copy link
Contributor

I may need to tweak something when this gets to the publishing system if the build checks find a problem, but it's good enough to check in here. Thanks @ericbrumer for the contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aq-pr-triaged Tracking label for the PR review team Change sent to author
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants