Add support for custom commands to set flags on themselves
This works for Python commands defined via a class (implement get_flags on your class) and C++ plugin commands (which can call SBCommand::GetFlags()/SetFlags()) Flags allow features such as not letting the command run if there's no target, or if the process is not stopped, ... Commands could always check for these things themselves, but having these accessible via flags makes custom commands more consistent with built-in ones llvm-svn: 238286
This commit is contained in:
@@ -330,7 +330,7 @@ class CommandObjectRenderScriptRuntimeModuleProbe : public CommandObjectParsed
|
||||
: CommandObjectParsed(interpreter, "renderscript module probe",
|
||||
"Initiates a Probe of all loaded modules for kernels and other renderscript objects.",
|
||||
"renderscript module probe",
|
||||
eFlagRequiresTarget | eFlagRequiresProcess | eFlagProcessMustBeLaunched)
|
||||
eCommandRequiresTarget | eCommandRequiresProcess | eCommandProcessMustBeLaunched)
|
||||
{
|
||||
}
|
||||
|
||||
@@ -368,7 +368,7 @@ class CommandObjectRenderScriptRuntimeModuleDump : public CommandObjectParsed
|
||||
CommandObjectRenderScriptRuntimeModuleDump(CommandInterpreter &interpreter)
|
||||
: CommandObjectParsed(interpreter, "renderscript module dump",
|
||||
"Dumps renderscript specific information for all modules.", "renderscript module dump",
|
||||
eFlagRequiresProcess | eFlagProcessMustBeLaunched)
|
||||
eCommandRequiresProcess | eCommandProcessMustBeLaunched)
|
||||
{
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user