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
21 lines
718 B
OpenEdge ABL
21 lines
718 B
OpenEdge ABL
STRING_EXTENSION_OUTSIDE(SBCommandReturnObject)
|
|
|
|
%extend lldb::SBCommandReturnObject {
|
|
// transfer_ownership does nothing, and is here for compatibility with
|
|
// old scripts. Ownership is tracked by reference count in the ordinary way.
|
|
|
|
void SetImmediateOutputFile(lldb::FileSP BORROWED, bool transfer_ownership) {
|
|
self->SetImmediateOutputFile(BORROWED);
|
|
}
|
|
void SetImmediateErrorFile(lldb::FileSP BORROWED, bool transfer_ownership) {
|
|
self->SetImmediateErrorFile(BORROWED);
|
|
}
|
|
|
|
// wrapping the variadic Printf() with a plain Print()
|
|
// because it is hard to support varargs in SWIG bridgings
|
|
void Print (const char* str)
|
|
{
|
|
self->Printf("%s", str);
|
|
}
|
|
}
|