[Lldb-commits] [lldb-dev] [lldb] r253317 - Add Pythonic language binding wrapper generation script.

Zachary Turner via lldb-commits lldb-commits at lists.llvm.org
Wed Nov 18 12:45:22 PST 2015

On Wed, Nov 18, 2015 at 11:15 AM Todd Fiala <todd.fiala at gmail.com> wrote:

> On Wed, Nov 18, 2015 at 10:34 AM, Zachary Turner <zturner at google.com>
> wrote:
>>   Because even if it isn't perfect for everyone, it works for everyone.
> Unless you can't get swig on your system in a way that doesn't break other
> items.  And then it doesn't work (as things stand now).
Is that a real issue that people on OSX are facing now?  Because I thought
having SWIG installed on your system has been a requirement for the past N
years.  Did something change  recently that now makes it impossible to
install swig in a way that doesn't break something?

>> And there is inherent simplicity in having fewer ways to do things, as
>> well as reducing maintenance cost.
>>> So for the more common, casual lldb build environment where the
>>> developer is not touching SB API, help me understand how reducing the need
>>> for swig (without introducing the need for hitting another server) is
>>> increasing the requirement load?  (Especially if we --- our local dev group
>>> sitting by me --- maintains those static bindings)?
>> Well, we would need to disable static bindings on the OSX buildbots for
>> starters, otherwise when someone not using static bindings makes a change,
>> the buildbots break, and we cannot leave buildbots in a broken state.  So I
>> assume that will still be possible.  So now you don't have a buildbot
>> testing the static binding configuration.
> I was actually going to add a verifier stage to the public OS X buildbot.
I'm not sure I follow this point.  What would your verifier stage do?  I'm
imagining the following scenario:

I check in some changes to SWIG interface files at like 10PM.  Ignoring the
fact that you and Jason are usually up firing commits away until the wee
hours of the morning, let's pretend nobody sees this until the morning.  So
the build bot has been broken all night.  Is this something that is going
to happen under this scenario?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20151118/6fd7f6d8/attachment.html>

More information about the lldb-commits mailing list