/external/webkit/Tools/Scripts/webkitpy/tool/ |
multicommandtool.py | 32 # tool-name [global options] command-name [command options] 38 from webkitpy.tool.grammar import pluralize 57 # option_parser can be overriden by the tool using set_option_parser 62 # the tool to be able to create and modify the option_parser 73 # The tool calls bind_to_tool on each Command after adding it to its list. 74 def bind_to_tool(self, tool): 75 # Command instances can only be bound to one tool at a time. 76 if self._tool and tool != self._tool: 77 raise Exception("Command already bound to tool!") 78 self._tool = tool [all...] |
/frameworks/base/docs/html/training/multiple-apks/ |
index.jd | 54 configuration using the <code>aapt</code> tool before pushing live.</dd> 59 using the <code>aapt</code> tool before pushing live.</dd> 64 configuration using the <code>aapt</code> tool before pushing live.</dd> 70 manifest, and how to investigate your APK configuration using the <code>aapt</code> tool before
|
/frameworks/base/tools/localize/ |
Android.mk | 4 # Android Asset Packaging Tool
|
/frameworks/compile/libbcc/runtime/make/ |
config.mk | 12 # Tool configuration variables.
|
/ndk/tests/ |
README | 15 on an Android device. To run them, call "run-tests.sh" with the "adb" tool
|
/packages/experimental/ |
README | 4 harness, development tool, or general fun times.
|
/sdk/layoutlib_api/sample/testproject/ |
build.xml | 5 tool. 11 by the 'android' tool. This is the place to change some of the 21 be updated using the 'android' tool with the 'update' action. 30 tool, as well as ADT.
|
/sdk/templates/ |
build.template | 4 <!-- The local.properties file is created and updated by the 'android' tool. 10 'android' tool to add properties to it. 23 be updated using the 'android' tool with the 'update' action. 32 tool, as well as ADT.
|
/sdk/testapps/basicLib/ |
build.xml | 5 tool. 11 by the 'android' tool. This is the place to change some of the 21 be updated using the 'android' tool with the 'update' action. 30 tool, as well as ADT.
|
/sdk/testapps/basicLibWithJar/ |
build.xml | 5 tool. 11 by the 'android' tool. This is the place to change some of the 21 be updated using the 'android' tool with the 'update' action. 30 tool, as well as ADT.
|
/sdk/testapps/basicProject/ |
build.xml | 5 tool. 11 by the 'android' tool. This is the place to change some of the 21 be updated using the 'android' tool with the 'update' action. 30 tool, as well as ADT.
|
/sdk/testapps/basicProjectWithAidl/ |
build.xml | 5 tool. 11 by the 'android' tool. This is the place to change some of the 21 be updated using the 'android' tool with the 'update' action. 30 tool, as well as ADT.
|
/sdk/testapps/basicProjectWithJar/ |
build.xml | 5 tool. 11 by the 'android' tool. This is the place to change some of the 21 be updated using the 'android' tool with the 'update' action. 30 tool, as well as ADT.
|
/sdk/testapps/basicProjectWithLib/ |
build.xml | 5 tool. 11 by the 'android' tool. This is the place to change some of the 21 be updated using the 'android' tool with the 'update' action. 30 tool, as well as ADT.
|
/external/valgrind/main/docs/html/ |
lk-manual.html | 4 <title>13.?Lackey: an example tool</title> 9 <link rel="prev" href="bbv-manual.html" title="12.?BBV: an experimental basic block vector generation tool"> 10 <link rel="next" href="nl-manual.html" title="14.?Nulgrind: the minimal Valgrind tool"> 20 <div class="chapter" title="13.?Lackey: an example tool"> 22 <a name="lk-manual"></a>13.?Lackey: an example tool</h2></div></div></div> 30 <p>To use this tool, you must specify 31 <code class="option">--tool=lackey</code> on the Valgrind 36 <p>Lackey is a simple Valgrind tool that does various kinds of basic 38 program's code. It is primarily intended to be of use as an example tool, 122 <a accesskey="p" href="bbv-manual.html"><<?12.?BBV: an experimental basic block vector generation tool</a>?</td [all...] |
/external/webkit/Tools/Scripts/webkitpy/tool/commands/ |
download_unittest.py | 33 from webkitpy.tool.commands.commandtest import CommandsTest 34 from webkitpy.tool.commands.download import * 35 from webkitpy.tool.mocktool import MockCheckout, MockOptions, MockTool 41 tool = MockTool() 42 command.bind_to_tool(tool) 51 tool._checkout.commit_info_for_revision = lambda revision: mock_commit_info 65 self.assertRaises(ScriptError, command._prepare_state, options=None, args=["125 r122 123", "Reason"], tool=None) 66 self.assertRaises(ScriptError, command._prepare_state, options=None, args=["125 foo 123", "Reason"], tool=None) 114 self.assert_execute_outputs(Land(), [42], options=self._default_options(), expected_stderr=expected_stderr, tool=mock_tool) 123 self.assert_execute_outputs(Land(), [42], options=self._default_options(), expected_stderr=expected_stderr, tool=mock_tool [all...] |
/dalvik/dexdump/ |
Android.mk | 34 ## Build the device command line tool dexdump 63 ## Build the host command line tool dexdump
|
/external/clang/tools/diagtool/ |
diagtool_main.cpp | 20 if (DiagTool *tool = diagTools->getTool(argv[1])) 21 return tool->run(argc - 1, &argv[2], llvm::errs());
|
/external/javassist/src/main/javassist/tools/ |
Dump.java | 23 * Dump is a tool for viewing the class definition in the given 24 * class file. Unlike the JDK javap tool, Dump works even if
|
/external/libffi/testsuite/lib/ |
wrapper.exp | 19 # ${tool}_maybe_build_wrapper -- Build wrapper object if the target 24 proc ${tool}_maybe_build_wrapper { filename args } {
|
/external/oprofile/pp/ |
common_option.h | 38 * prototype of a pp tool entry point. This entry point is called 46 * @param fct function to run to start this pp tool
|
/external/v8/tools/visual_studio/ |
v8_base.vcproj | 23 <Tool 26 <Tool 29 <Tool 32 <Tool 35 <Tool 38 <Tool 41 <Tool 44 <Tool 47 <Tool 50 <Tool [all...] |
v8_base_x64.vcproj | 23 <Tool 26 <Tool 29 <Tool 32 <Tool 35 <Tool 38 <Tool 41 <Tool 44 <Tool 47 <Tool 50 <Tool [all...] |
/external/valgrind/main/ |
README_DEVELOPERS | 67 a particular tool) requires a bit more trickery but can be achieved 78 (2) Run gdb on the tool executable. Eg: 97 (5) Run the tool with required options: 107 puts the tool executable into a wait loop soon after it gains 112 GDB to the tool executable, which should be in the abovementioned 135 --tool=cachegrind -v inner/.../bin/valgrind --tool=none -v prog 149 When using self-hosting with an outer Callgrind tool, use '--pop-on-jump'
|
/external/valgrind/main/callgrind/docs/ |
callgrind_annotate-manpage.xml | 17 <refpurpose>post-processing tool for the Callgrind</refpurpose> 35 the Valgrind tool Callgrind and prints the information in an easy-to-read form.
|