Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support VS 2015 as well? #3862

Closed
davidfowl opened this issue Feb 3, 2015 · 7 comments
Closed

Support VS 2015 as well? #3862

davidfowl opened this issue Feb 3, 2015 · 7 comments
Labels
area-Infrastructure-coreclr help wanted [up-for-grabs] Good issue for external contributors

Comments

@davidfowl
Copy link
Member

Installation of VS 2013 is a pre-requisite to build this repository.

I don't want to have both installed on my machine. Does it rely on anything specifically in VS 2013?
@stephentoub stephentoub changed the title Support VS 2014 as well? Support VS 2015 as well? Feb 3, 2015
@gkhanna79 gkhanna79 self-assigned this Feb 3, 2015
@gkhanna79
Copy link
Member

Hi David,

Bringing VS 2015 support is of the top items on our list. Stayed tuned.

@davidfowl
Copy link
Member Author

✨

@MattWhilden
Copy link
Contributor

Anyone know what state this is in?

@MattWhilden
Copy link
Contributor

I spoke to some follks around here about this and this is obviously still on the roadmap. Marking it as up-for-grabs because we believe that anyone with some gumption and VS2015 could get this put together. When things settle down internally, we'll pick this up if it's not corrected.

richlander referenced this issue in dotnet/coreclr Apr 26, 2015
@richlander
Update windows-instructions.md
f185bf3 
- Added reference to issue #30 so that people can "watch at home" on this issue.
@ghost
Copy link

ghost commented Jun 3, 2015

@DickvdBrink and I can build coreclr master on VS2015 RC, https://github.com/dotnet/coreclr/issues/1033#issuecomment-104688632. Please reconfirm and update this.

@DickvdBrink
Copy link
Contributor

@jasonwilliams200OK, there seems to be something wrong now.. creating a debug build works but a release build fails with some jit issues I believe.

@ghost
Copy link

ghost commented Jun 4, 2015

@DickvdBrink, yes, mostly unresolved symbols in WKS etc. I am getting Linker errors in release configuration.

@gkhanna79 gkhanna79 removed their assignment Feb 1, 2016
BruceForstall referenced this issue in BruceForstall/coreclr Aug 12, 2016
@pgavlin
Merge pull request #30 from pgavlin/LIRDumpUpdates
23dfb61 
Update LIR dumps.
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 30, 2020
This was referenced Jan 30, 2020
Closed
Closed
@brianrob brianrob mentioned this issue Jan 31, 2020
Closed
@ghost ghost locked as resolved and limited conversation to collaborators Jan 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-Infrastructure-coreclr help wanted [up-for-grabs] Good issue for external contributors
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@davidfowl @DickvdBrink @gkhanna79 @MattWhilden