-
Notifications
You must be signed in to change notification settings - Fork 768
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
msvc: Allow building with Visual Studio Preview versions #1711
Conversation
Thanks for the pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 2 LGTMs obtained (waiting on @sankhesh)
build.py
line 129 at r1 (raw file):
print( "Calling vswhere -latest -installationVersion" ) latest_full_v = subprocess.check_output( [ VSWHERE_EXE, '-latest', '-prerelease', '-property', 'installationVersion' ]
Please can you explain canonically what this does? We don’t want to always use prerelease versions. In fact I’d rather not support them at all as we will never test with them. I’m happy to make it work by chance or by opt-in, but not by default.
With The current code defaults to the latest without user opt-in/choice if there are multiple versions. This change just extends it further to allow latest Preview versions as well. Note that without this change, if I just have VS Preview version installed (with valid MSVC compiler), ycmd build fails with the error that MSVC could not be found. |
If I have both a released and pre-release version, which is picked? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: 0 of 2 LGTMs obtained (waiting on @sankhesh)
a discussion (no related file):
Flake8 error means ci is broken. Line too long.
I am not an expert but IMHO, because of the
Thanks, I'll fix that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am in favour of this. MS takes ages between two non-preview releases and I know that some people do use latest preview only. Plus MS likes to write blog posts about how latest preview versions are the bestest.
@sankhesh Would you mind using reviewable for the review. It helps keep discussion threads in order and has some nice features.
Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: 1 of 2 LGTMs obtained (waiting on @sankhesh)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure 👍
Reviewable status: 0 of 2 LGTMs obtained (and 1 stale) (waiting on @bstaletic and @puremourning)
a discussion (no related file):
Previously, puremourning (Ben Jackson) wrote…
Flake8 error means ci is broken. Line too long.
Done.
build.py
line 129 at r1 (raw file):
Previously, puremourning (Ben Jackson) wrote…
Please can you explain canonically what this does? We don’t want to always use prerelease versions. In fact I’d rather not support them at all as we will never test with them. I’m happy to make it work by chance or by opt-in, but not by default.
Done
Hmm.. I don't know why that CI is failing. |
It happens. Windows jobs are a little flakey. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #1711 +/- ##
==========================================
- Coverage 95.42% 95.41% -0.01%
==========================================
Files 83 83
Lines 8123 8131 +8
Branches 164 165 +1
==========================================
+ Hits 7751 7758 +7
Misses 322 322
- Partials 50 51 +1 |
@bstaletic @puremourning Good to merge? |
I am ok with this pull request, but @puremourning said he would prefer this to be opt-in.
So could you add an option like |
This flag allows compiling against the latest MSVC preview version. By default, this is disabled; meaning only the latest stable MSVC release is used.
1c991f8
to
aba1b1d
Compare
@bstaletic @puremourning The latest commit adds the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!
Reviewed 1 of 1 files at r4, all commit messages.
Reviewable status: 1 of 2 LGTMs obtained (and 1 stale) (waiting on @sankhesh)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewable status: complete! 2 of 2 LGTMs obtained (and 1 stale) (waiting on @puremourning)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r4, all commit messages.
Reviewable status: complete! 2 of 2 LGTMs obtained (and 1 stale) (waiting on @puremourning)
Thanks for sending a PR! |
1 similar comment
Thanks for sending a PR! |
@bstaletic @puremourning Anything else needed here? |
Well, CI is failing, so we will need to resolve that before merging. |
Thanks for sending a PR! |
This change allows compiling ycmd against latest Visual Studio Preview versions.
Tested against Visual Studio 2022 Community version 17.8.0 Preview 2.0.
This change is