[lldb-dev] Default script language

[Jim Ingham via lldb-dev]

Right now, Lua is not nearly as well supported as Python, so it makes sense that if both Python and Lua are available Python should be the default.  But at some point Lua will become an equal to Python.  When that happens, it seems to me the default scripting language choice should be up to the package distributor.  I don’t see why we need to weigh in on that.  That would imply that the default should be an independent build setting.  Not sure that means we need to do it that way now, but if we don’t want to do it twice…

Jim


> On Apr 1, 2020, at 2:09 PM, Ed Maste via lldb-dev <lldb-dev at 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 at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev