On Wed, 1 Apr 2020 at 19:13, Ted Woodward <tedw...@quicinc.com> wrote: > > I agree with Jim - it should be a cmake setting, defaulting to Python. If the > person building lldb wants to change the default scripting language from > Python to Lua, it should be easy.
Ok, agreed. My initial concern was that python remained the default even if not compiled in, but I can carry a tiny patch in the FreeBSD base system to address that for now. I agree with Jim that there's no point in doing the work twice. > Since we now support 2 scripting languages, we should have an easy way for > the user to see which are supported, and which is the default if there are > more than 1 supported. Maybe in lldb --version? We should indeed have a way to see which languages are available and which is default. We have a few other build-time options, should we include a summary of all of them in --version I wonder? On Thu, 2 Apr 2020 at 02:44, Pavel Labath <pa...@labath.sk> wrote: > > That said, I don't think we can implement this using #ifdefs. > lldb-enumerations.h is a part of our public api, Config.h isn't (it > theoretically could be, but I don't think we want that). As it turns out changing lldb-enumerations.h wasn't sufficient anyway, the default is also specified in CoreProperties.td. I'll start looking into both of these changes (dealing with eScriptLanguageDefault, and adding cmake configuration). _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
