[lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

[Ted Woodward via lldb-dev]

Yours is Win Server 2008; ours is Win 7. I don’t know if that matters.

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

 

From: Zachary Turner [mailto:zturner at google.com] 
Sent: Tuesday, February 02, 2016 2:48 PM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

 

If I remember correctly your bot isn't actually doing anything differently than my bot [http://lab.llvm.org:8011/builders/lldb-x86-windows-msvc2015].  If you want you could just remove your bot.  If you want to keep it, then yea getting it on VS2015 and Python 3 would be the best idea.

 

On Tue, Feb 2, 2016 at 12:20 PM Ted Woodward via lldb-dev <lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org> > wrote:

It looks like our bot, http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc , has tried to update to Python 3.5 and MSVC 2015, but it can’t find python or VC. I’ll talk to our buildmiester about it.

 

Should we run this guy with 2013/py2.7 or 2015/py3.5?

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

 

From: lldb-dev [mailto:lldb-dev-bounces at lists.llvm.org <mailto:lldb-dev-bounces at lists.llvm.org> ] On Behalf Of Zachary Turner via lldb-dev
Sent: Tuesday, February 02, 2016 1:55 PM
To: Tamas Berghammer; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported toolchain

 

 

On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer <tberghammer at google.com <mailto:tberghammer at google.com> > wrote:

Hi Zachary,

 

We are still using MSVC 2013 and Python 2.7 to compile LLDB on Windows for Android Studio and we also have a buildbot what is testing this configuration (without sending e-mail at the moment) here: http://lab.llvm.org:8011/builders/lldb-windows7-android

 

We are in the discussion to decide what is our plan for going forward both in terms of Visual Studio version and Python version and I expect that we will make a decision this week. Until then please don't remove any hack we have in the code because of MSVC 2013 (e.g. alias template workarounds) and if adding new code then please try not to break MSVC 2013. I will send out an update about our decision hopefully at the end of this week.

Yea I mentioned already that I'm not planning on removing anything related to MSVC 2013, just that I'm personally not supporting it.  Which means that if anyone asks for help, or wants to make it work, or if it breaks accidentally, they're on their own :)  I don't even have MSVC 2013 installed on my machine anymore, so I can't fix any MSVC 2013 specific issues that arise.

 

Of course if someone else comes along and wants to help, I have no problem with that, but due to the difficulty of dealing with incompatibility between Python 2 and MSVC 2015, it's just going to be up to someone else to continue making that work if they need it.

 

 

You mentioned that LLVM plan to bump the minimum version of MSVC to 2015. Do you have any link to the place where they discussed it or do you know anything about the schedule?

 

As far as I know the discussion hasn't started yet, but historically LLVM has always been pretty consistent about bumping the required MSVC version every 12-18 months.   I know some of the Windows people on the LLVM side are already "unoficially" using MSVC 2015 on a regular basis, and that's usually a sign that people are getting an early start to see what kind of issues might be encountered by the general public when bumping the required version.

_______________________________________________
lldb-dev mailing list
lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org> 
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20160202/53d09991/attachment.html>