: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported
toolchain
Keep in mind that llvm bumps minimum vs version roughly once a year, and it's
probably about that time. So the discussion here is just about whether to do it
earlier than llvm, not whether to do it all.
So whether
gt;
> >> --
> >> Qualcomm Innovation Center, Inc.
> >> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
> a Linux Foundation Collaborative Project
> >>
> >> -----Original Message-----
> >> From: Pavel Labath [mailto:lab...@goog
Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
From: Zachary Turner [mailto:ztur...@google.com]
Sent: Tuesday, February 02, 2016 5:28 PM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving t
Pavel Labath [mailto:lab...@google.com]
> > Sent: Thursday, February 04, 2016 10:01 AM
> > To: Ted Woodward
> > Cc: Zachary Turner; LLDB
> > Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
> unsupported toolchain
> >
> > Hi all.
> >
> > w
t; To: Ted Woodward
> Cc: Zachary Turner; LLDB
> Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported
> toolchain
>
> Hi all.
>
> we (android lldb team) are starting to transition to VS2015 as well.
> For now, the plan is to stick to python 2.7, but if we enc
mailto:lab...@google.com]
Sent: Thursday, February 04, 2016 10:01 AM
To: Ted Woodward
Cc: Zachary Turner; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported
toolchain
Hi all.
we (android lldb team) are starting to transition to VS2015 as well.
For now, the plan is to stick
http://lab.llvm.org:8011/builders/lldb-x86-win7-msvc/builds/15168
>> >
>> >
>> >
>> > It went red because of the change to VS2015/Python 3.5.
>> >
>> >
>> >
>> > --
>> >
>> > Qualcomm Innovation Center, Inc.
fident that test
> > coverage is going to be 100% the same across both. It's just a matter
> of if
> > you want to have something that you maintain / have control over, or if
> you
> > want to test something in a different way than what we're testing.
> >
>
equires 2015.
>
>
>
> --
>
> 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:ztur...@google.com]
> Sent: Tuesday, February
Project
From: Zachary Turner [mailto:ztur...@google.com <mailto:ztur...@google.com> ]
Sent: Tuesday, February 02, 2016 3:43 PM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported
toolchain
It's Server 2008 R2 technically, which is the s
Collaborative Project
>>
>>
>>
>> *From:* Zachary Turner [mailto:ztur...@google.com]
>> *Sent:* Tuesday, February 02, 2016 3:43 PM
>>
>>
>> *To:* Ted Woodward; LLDB
>> *Subject:* Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an
>> unsupport
k 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
>
&g
, February 02, 2016 3:43 PM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] MSVC 2013 w/ Python 2.7 is moving to an unsupported
toolchain
It's Server 2008 R2 technically, which is the server version of Win 7 (same API
set, same OS features, etc). So yea, I'm pretty confident that test co
he Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
>
>
> *From:* Zachary Turner [mailto:ztur...@google.com]
> *Sent:* Tuesday, February 02, 2016 2:48 PM
> *To:* Ted Woodward; LLDB
>
>
> *Subject:* R
, 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]. I
t; *From:* lldb-dev [mailto:lldb-dev-boun...@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
>
>
: [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 mailto:tbergham...@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
On Tue, Feb 2, 2016 at 11:42 AM Tamas Berghammer
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
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 dec
As of this week, we have the test suite running clean under MSVC 2015 using
Python 3.5. I'm sure new things will pop up, but I'm considering the
transition "done" as of now.
What this means for MSVC 2013 is that we dont' want to support it anymore.
Reasons:
* C++ language support is poor
* Compi
20 matches
Mail list logo
