662548c826
Instead of maintaining separate swig interface files, we can use the API headers directly. They implement the exact same C++ APIs and we can conditionally include the python extensions as needed. To remove the swig extensions from the API headers when building the LLDB framework, we can use the unifdef tool when it is available. Otherwise we just copy them as-is. Differential Revision: https://reviews.llvm.org/D142926
11 lines
568 B
OpenEdge ABL
11 lines
568 B
OpenEdge ABL
%extend lldb::SBExecutionContext {
|
|
#ifdef SWIGPYTHON
|
|
%pythoncode %{
|
|
target = property(GetTarget, None, doc='''A read only property that returns the same result as GetTarget().''')
|
|
process = property(GetProcess, None, doc='''A read only property that returns the same result as GetProcess().''')
|
|
thread = property(GetThread, None, doc='''A read only property that returns the same result as GetThread().''')
|
|
frame = property(GetFrame, None, doc='''A read only property that returns the same result as GetFrame().''')
|
|
%}
|
|
#endif
|
|
}
|