if you look at binding-generation-as-service element...

Subprojects LLDB
1

Hey Zachary,

Please make sure to ping Greg Clayton, particularly if it does anything that would make the binding no longer be C-linkage-compatible. He can tell you all the bits we are counting on. I think the keys are:

  • we don’t ever have there be vtables.
  • we never remove API surface area.
  • we don’t change signatures of existing API.

but I don’t think that’s exhaustive and certainly not authoritative.

Anyways, just make sure you sync up with him so you don’t end up wasting any energy on something that will break some kind of requirement we have.

Thanks!

2

Can I send you a sample set of bindings generated by 3.x as a fail-fast test? Try them out, see if anything breaks, etc?

3

Sure.

4

LLDBWrapPython.cpp
lldb.py

Double check the top of lldb.py to make sure swig_version = (3,0,x)

5

Err, links aren’t showing up for me. Gonna try this again.

lldb.py - https://drive.google.com/file/d/0Bzpf8QJC6OGOaEVaNF9GY0tPXzg/view?usp=sharing

LLDBWrapPython.cpp - https://drive.google.com/file/d/0Bzpf8QJC6OGOaEVaNF9GY0tPXzg/view?usp=sharing

6

Google Drive is being bad right now. Hopefully this works better :-/

scripts.tar.gz (272 KB)

7

Ah good got it. Thanks, somehow didn’t see this earlier. Thanks!