?
>
>
>
> --
>
> 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:* Wednesday, Decemb
PM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] swig generation and "six" module
What about requiring that the user has done "pip install six" on their machine?
On Wed, Dec 9, 2015 at 1:40 PM Ted Woodward via lldb-dev
mailto:lldb-dev@lists.llvm.org> &g
What about requiring that the user has done "pip install six" on their
machine?
On Wed, Dec 9, 2015 at 1:40 PM Ted Woodward via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> r252764 changes finishSwigPythonLLDB.py to symlink the “six” module in
> site-packages. six.py is a symlink to
> /tools/lldb
r252764 changes finishSwigPythonLLDB.py to symlink the "six" module in
site-packages. six.py is a symlink to
/tools/lldb/third_party/Python/module/six/six.py. This assumes I have
access to this build's sources when I run lldb, which I don't - our
workstations don't have access to the buildbots' fil
On Mon, Nov 16, 2015 at 11:28 PM, Todd Fiala wrote:
>
>
> On Fri, Nov 13, 2015 at 9:02 AM, Todd Fiala wrote:
>
>> Hi all,
>>
>> I'd like to do a few things with our swig generation and handling:
>>
>> * Create a maintainer-mode style setup where the swig Python bindings are
>> generated and chec
On Fri, Nov 13, 2015 at 9:02 AM, Todd Fiala wrote:
> Hi all,
>
> I'd like to do a few things with our swig generation and handling:
>
> * Create a maintainer-mode style setup where the swig Python bindings are
> generated and checked into the repo (I'll call it the static python
> binding).
>
> T
On Fri, Nov 13, 2015 at 10:24 AM Todd Fiala wrote:
> On Fri, Nov 13, 2015 at 9:43 AM, Zachary Turner
> wrote:
>
>> On Fri, Nov 13, 2015 at 9:02 AM Todd Fiala via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>>> Hi all,
>>>
>>> I'd like to do a few things with our swig generation and handling
I will probably tackle this as two phases:
Phase 1:
* Python script modernization (the python swig wrapper generation)
* Move Xcode onto it.
Phase 2:
* The maintainer-mode, static Python binding generation changes for cmake
and Xcode.
I want to make sure we have proven, still-functional Python f
On Fri, Nov 13, 2015 at 10:24 AM, Todd Fiala wrote:
>
>
> On Fri, Nov 13, 2015 at 9:43 AM, Zachary Turner
> wrote:
>
>> On Fri, Nov 13, 2015 at 9:02 AM Todd Fiala via lldb-dev <
>> lldb-dev@lists.llvm.org> wrote:
>>
>>> Hi all,
>>>
>>> I'd like to do a few things with our swig generation and han
On Fri, Nov 13, 2015 at 9:43 AM, Zachary Turner wrote:
> On Fri, Nov 13, 2015 at 9:02 AM Todd Fiala via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
>
>> Hi all,
>>
>> I'd like to do a few things with our swig generation and handling:
>>
>> * Create a maintainer-mode style setup where the swig Py
On Fri, Nov 13, 2015 at 9:02 AM Todd Fiala via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi all,
>
> I'd like to do a few things with our swig generation and handling:
>
> * Create a maintainer-mode style setup where the swig Python bindings are
> generated and checked into the repo (I'll call
Hi all,
I'd like to do a few things with our swig generation and handling:
* Create a maintainer-mode style setup where the swig Python bindings are
generated and checked into the repo (I'll call it the static python
binding).
This will be used by default, removing the need for most people and a
12 matches
Mail list logo
