-
Notifications
You must be signed in to change notification settings - Fork 4
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
Various fixes and housekeeping #17
Merged
Merged
Conversation
This file contains 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
- All compilers end up with a SETENV field with the actual script - All compilers now have a VERSION field - For compilers found with vswhere, it's the full version - For old SDK compilers, it's also the full version (from the registry) - For other compilers, it's the same as the key - The VC_VERSION and VSCMD_VER environment variables are captured and stored. Compilers without VSCMD_VER get an empty value; VisualStudioVersion is queried if VC_VERSION was not found (and the entry is empty otherwise).
The --installed switch displays a list of found Visual Studio installations without interrogating them further, and with slightly more information. It is faster than --all, since the installations are not queried for contents.
--output=data requires a single architecture and displays the resulting variables prefixed bin, inc or lib followed by '*' in native Windows format. The first line of the output is the full path to the batch file which was analysed by msvs-detect. The intention is that this output can be trivially parsed in another shell script.
MSVS_NAME was being treated as for PATH, LIB and INCLUDE for the environment compiler - it should be as for MSVS_ML.
x86 can now be referred to as 86, x86 or x86_32 x64 can now be referred to as 64, x64 or x86_64
When selecting a complementary compiler (e.g. requesting x64 where the environment is x86), the x64 compiler of the environment compiler's installation should be preferred.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Functional changes:
-prerelease
tovswhere
)--installed
. Essentially an early exit before probing and testing the installations, so it's much faster than--all
--output=data
. Intended to allow the output ofmsvs-detect
to be parsed by another shell scriptMSVS_NAME
is always set, even for an environment compilerx86_32
andx86_64
architecture aliases--arch
to ensure that the environment compiler is always preferred (otherwise complementary compiler detection is counterintuitive)Housekeeping: