-
Notifications
You must be signed in to change notification settings - Fork 463
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
EXTERNAL_INCLUDE env variable is not imported from VS dev environment #4217
Comments
@equeim Thanks for your github question! In order to better reproduce your problem and fix it, could you give us a detailed reproduction step-by-step and some additional information? |
Sure.
Expected result:
During build there are no warnings. Actual result:
When building this project in command line inside VS developer environment the behaviour matches one in "Expected result". |
@equeim Thank you for your help! We can reproduce this issue based the above information. We have been changed this issue to bug, please be patient with the results of our investigation and we will notify you of any updates as soon as they are available! @gcampbell-msft We can reproduce the issue on latest CMake Tools version 1.20.32(pre-release) and change the Label to ‘Bug’ for now, if it is wrong could you please change it to the correct label, the reproduction steps are detailed below. Thanks! Repro steps:
Actual result: |
Brief Issue Summary
Running
C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools\Launch-VsDevShell.ps1
script in PowerShell sets, among others, aEXTERNAL_INCLUDE
environment variable with this (example) value:This env variable is (I assume) used by MSVC as an alternative to
/external:I
option (https://learn.microsoft.com/en-us/cpp/build/reference/external-external-headers-diagnostics).However this extension does not import it, which results in unnecessary compilation warnings from external headers that should be hidden by default (#4215).
CMake Tools Diagnostics
Debug Log
Additional Information
Here is what
C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools\Launch-VsDevShell.ps1
sets for me:The text was updated successfully, but these errors were encountered: