For scripting to working it must support classes and Swig must support creating bindings for the entire public API. Don't think shell scripting can do that.
Greg > On Apr 1, 2020, at 3:24 PM, Marcus Johnson via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > Why default to none if python and lua aren't available instead of defaulting > to shell scripting? > >> On Apr 1, 2020, at 5:09 PM, Ed Maste via lldb-dev <lldb-dev@lists.llvm.org> >> wrote: >> >> In lldb/include/lldb/lldb-enumerations.h we have: >> eScriptLanguageDefault = eScriptLanguagePython >> >> I'd like to do something like: >> #if LLDB_ENABLE_PYTHON >> eScriptLanguageDefault = eScriptLanguagePython >> #elif LLDB_ENABLE_LUA >> eScriptLanguageDefault = eScriptLanguageLua >> #else >> eScriptLanguageDefault = eScriptLanguageNone >> #endif >> >> if we could include Config.h, or achieve the same effect in some other >> way if we cannot. Does this seem reasonable? >> >> I'm interested in this for lldb in the FreeBSD base system. We have >> lua available already (and no python) and I've integrated our liblua >> it into lldb, but it required "--script-language lua" on the command >> line. For now I'll just change the default to be eScriptLanguageLua in >> our tree, but would like to have this "just work" upstream. >> _______________________________________________ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
