| /external/chromium/chrome/common/net/ |
| x509_certificate_model_nss.cc | 42 // (It's a bit redundant that the caller needs to specify len in addition to the
|
| /external/chromium/googleurl/base/ |
| logging.cc | 86 // nobody has called InitLogging to specify a debug log file, so here we
|
| /external/chromium/testing/gtest/samples/ |
| sample6_unittest.cc | 90 // to declare it and specify the type parameters. As with TEST_F,
|
| /external/chromium/testing/gtest/scripts/ |
| fuse_gtest_files.py | 95 print ('Please either specify a valid project root directory '
|
| /external/chromium-trace/ |
| systrace.py | 75 help='specify a comma-separated list of kernel functions to trace')
|
| /external/chromium-trace/trace-viewer/build/ |
| parse_deps.py | 314 The javascript files shoud specify their dependencies in a format that is
|
| /external/chromium-trace/trace-viewer/src/ |
| model.js | 240 * traces are to be imported, specify the first one as events, and the
|
| /external/chromium-trace/trace-viewer/third_party/pywebsocket/src/example/ |
| echo_client.py | 168 and raises an ClientHandshakeError on failure. You can specify case
524 'Specify the origin of the connection by --origin flag')
744 'Specify the origin of the connection by --origin flag')
[all...] |
| /external/clang/ |
| NOTES.txt | 56 (1) If the user does not specify -triple, we default to the host triple.
|
| /external/clang/docs/ |
| HowToSetupToolingForLLVM.rst | 17 invoking clang tools, you can either specify a path to a build directory
|
| /external/clang/docs/analyzer/ |
| RegionStore.txt | 109 explicitly specify a binding for each individual element.
|
| /external/clang/include/clang/Driver/ |
| CC1Options.td | 31 HelpText<"Specify target triple (e.g. i686-apple-darwin9)">;
85 HelpText<"Specify the function selection heuristic used during inlining">;
399 HelpText<"Specify the class to use for constant Objective-C string objects.">;
467 HelpText<"Specify the name of the module to build">;
|
| /external/clang/lib/StaticAnalyzer/ |
| README.txt | 114 The first allows you to specify only analyzing a specific function.
|
| /external/dexmaker/src/dx/java/com/android/dx/ssa/ |
| PhiInsn.java | 333 * allows sub-classes to specify extra text.
|
| /external/e2fsprogs/ext2ed/ |
| README | 120 directory above, use the TERMINFO environment variable to specify
|
| /external/e2fsprogs/lib/ext2fs/ |
| openfs.c | 155 * superblock, then he/she must also specify the block size!
|
| /external/e2fsprogs/misc/ |
| blkid.c | 389 /* If we didn't specify a single device, show all available devices */
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.6.1.R36x_v20100823/templates/headless-build/ |
| build.properties | 234 # Specify the output format of the compiler log when eclipse jdt is used
|
| customAssembly.xml | 63 <echo message="You must specify a target when invoking this file" />
|
| /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/ |
| readme.html | 20 'N' builds preceding the current build.</li><li>This can be overriden with the use of the "-current.prefix" parameter where you can specify a comma-separated list of prefixes for build ids to include in the main line graph.<br> <br> </li></ul></li><li>Scenario names
|
| /external/elfutils/src/ |
| arlib.c | 62 NUL byte. We could use a trick whereby we specify the target
|
| /external/grub/netboot/ |
| Makefile.am | 60 # Is it really necessary to specify dependecies explicitly?
|
| /external/grub/stage2/ |
| Makefile.am | 119 # XXX: automake doesn't provide a way to specify dependencies for object
|
| /external/gtest/samples/ |
| sample6_unittest.cc | 90 // to declare it and specify the type parameters. As with TEST_F,
|
| /external/gtest/scripts/ |
| fuse_gtest_files.py | 95 print ('Please either specify a valid project root directory '
|
