Searched refs:own (Results 1 – 25 of 777) sorted by relevance
12345678910>>...32
/external/chromium/chrome/browser/chromeos/cros/ |
D | cros_library.h | 58 void SetLibraryLoader(LibraryLoader* loader, bool own); 59 void SetBrightnessLibrary(BrightnessLibrary* library, bool own); 60 void SetBurnLibrary(BurnLibrary* library, bool own); 61 void SetCryptohomeLibrary(CryptohomeLibrary* library, bool own); 62 void SetInputMethodLibrary(InputMethodLibrary* library, bool own); 63 void SetLibCrosServiceLibrary(LibCrosServiceLibrary* library, bool own); 64 void SetLoginLibrary(LoginLibrary* library, bool own); 65 void SetMountLibrary(MountLibrary* library, bool own); 66 void SetNetworkLibrary(NetworkLibrary* library, bool own); 67 void SetPowerLibrary(PowerLibrary* library, bool own); [all …]
|
D | cros_library.cc | 31 class_prefix##Library* library, bool own) { \ 32 library_->var_prefix##_lib_.SetImpl(library, own); \ 103 void CrosLibrary::TestApi::SetLibraryLoader(LibraryLoader* loader, bool own) { in SetLibraryLoader() argument 108 library_->own_library_loader_ = own; in SetLibraryLoader()
|
/external/wpa_supplicant_8/wpa_supplicant/dbus/ |
D | dbus-wpa_supplicant.conf | 6 <allow own="fi.epitest.hostap.WPASupplicant"/> 11 <allow own="fi.w1.wpa_supplicant1"/> 18 <deny own="fi.epitest.hostap.WPASupplicant"/> 22 <deny own="fi.w1.wpa_supplicant1"/>
|
/external/dnsmasq/dbus/ |
D | dnsmasq.conf | 6 <allow own="uk.org.thekelleys.dnsmasq"/> 10 <deny own="uk.org.thekelleys.dnsmasq"/>
|
/external/clang/test/SemaObjC/ |
D | warn-deprecated-implementations.m | 18 + (void)F { } // No warning, implementing its own deprecated method 28 - (void) G {} // No warning, implementing its own deprecated method
|
/external/v8/test/mjsunit/ |
D | array-pop.js | 74 var own = a.hasOwnProperty(j); 100 var own = a.hasOwnProperty(j);
|
/external/antlr/antlr-3.4/runtime/C/doxygen/ |
D | buildrec.dox | 58 /// // You may adopt your own practices by all means, but in general it is best 61 /// // multiple times) and your own project related header files. Use <> to include and 97 /// // You can create your own input stream type (copy one of the existing ones) and override a… 98 /// // individual function by installing your own pointer after you have created the standard 112 /// // supplied to the generated parser, and you can write your own token stream and pass this … 133 /// // out the nodes upon request. You can make your own tree types and adaptors 192 /// // Note tha even if you implement your own token structure, it will always 195 /// // it that should point to your own outer token structure. 237 /// // keeping your own flags as part of the error trapping, but here is how you can
|
D | doxygengroups.dox | 15 /// your own function. Some of these methods create other 'objects' (instances of 16 /// typedef structures), which allows you install your own method and create your 17 /// own implementation of these. 31 /// then override any part of the implementation by installing your own 36 /// your own. In your grammar, you would place the following 49 /// install your own implementations of the #ANTLR3_BASE_RECOGNIZER interface
|
/external/protobuf/vsprojects/ |
D | readme.txt | 51 own install directory. C++ makes it very difficult to maintain binary 71 your own project as well, so you should probably just put them into the 80 against the zlib library directly from your own app. 89 and compiler. You may have to disable some of them in your own project as 109 end up compiling instances of the templates into their own binary. The
|
/external/eigen/doc/ |
D | TopicMultithreading.dox | 30 In the case your own application is multithreaded, and multiple threads make calls to Eigen, then y… 42 In the case your application is parallelized with OpenMP, you might want to disable Eigen's own par…
|
/external/gtest/ |
D | README | 63 build Google Test and its own tests from an SVN checkout (described 141 Test's own tests. Instead, it just builds the Google Test library and 142 a sample test. You can use it as a starting point for your own build 238 enough for its own need, and will automatically use this when the 250 you want to force Google Test to use its own tuple library, just add 281 script, this is taken care of for you. If you use your own build 348 You may need to explicitly enable or disable Google Test's own TR1 355 supportted. You are encouraged to migrate to your own build system or 372 This section discusses how to make your own changes to Google Test. 377 functionality, you'll want to compile and run Google Test's own tests. [all …]
|
/external/chromium/testing/gtest/ |
D | README | 63 build Google Test and its own tests from an SVN checkout (described 141 Test's own tests. Instead, it just builds the Google Test library and 142 a sample test. You can use it as a starting point for your own build 238 enough for its own need, and will automatically use this when the 250 you want to force Google Test to use its own tuple library, just add 281 script, this is taken care of for you. If you use your own build 348 You may need to explicitly enable or disable Google Test's own TR1 355 supportted. You are encouraged to migrate to your own build system or 372 This section discusses how to make your own changes to Google Test. 377 functionality, you'll want to compile and run Google Test's own tests. [all …]
|
D | CMakeLists.txt | 19 option(gtest_build_tests "Build all of gtest's own tests." OFF) 97 # Google Test's own tests. 172 # That declaration conflicts with our own standard-conforming 173 # tuple implementation. Therefore using our own tuple with
|
/external/libvpx/libvpx/third_party/googletest/src/ |
D | README | 63 build Google Test and its own tests from an SVN checkout (described 141 Test's own tests. Instead, it just builds the Google Test library and 142 a sample test. You can use it as a starting point for your own build 238 enough for its own need, and will automatically use this when the 250 you want to force Google Test to use its own tuple library, just add 281 script, this is taken care of for you. If you use your own build 348 You may need to explicitly enable or disable Google Test's own TR1 355 supportted. You are encouraged to migrate to your own build system or 372 This section discusses how to make your own changes to Google Test. 377 functionality, you'll want to compile and run Google Test's own tests. [all …]
|
D | CMakeLists.txt | 19 option(gtest_build_tests "Build all of gtest's own tests." OFF) 97 # Google Test's own tests. 172 # That declaration conflicts with our own standard-conforming 173 # tuple implementation. Therefore using our own tuple with
|
/external/chromium/googleurl/base/ |
D | README.txt | 1 These files contain some shared code. You can define your own assertion macros
|
/external/iptables/include/iptables/ |
D | internal.h.in | 7 * Program's own name and version.
|
/external/sepolicy/ |
D | shell.te | 7 # XXX Split into its own domain?
|
/external/doclava/res/assets/templates/ |
D | components.cs | 2 <?cs # Use the -tempatedir arg to javadoc to set your own directory with a replacement for this fil…
|
/external/llvm/test/Verifier/ |
D | SelfReferential.ll | 1 ; RUN: not llvm-as %s -o /dev/null 2>&1 | grep "Only PHI nodes may reference their own value"
|
/external/e2fsprogs/lib/uuid/ |
D | configure.in | 3 dnl own package.
|
/external/antlr/antlr-3.4/antlr3-maven-archetype/src/main/resources/archetype-resources/src/main/antlr3/imports/ |
D | Ruleb.g | 4 // own imports directory: src/main/antlr3/imports
|
/external/stlport/ |
D | README.google | 7 * _mbstate_t.h cannot define its own mbstate_t as bionic already defines
|
/external/ppp/pppd/plugins/pppoatm/ |
D | COPYING | 6 The file pppoatm.c contains its own copyright notice, and is licensed
|
/external/webkit/LayoutTests/storage/domstorage/localstorage/ |
D | window-open-expected.txt | 5 Value for FOO after changing my own copy is BAR-NEWWINDOW
|
12345678910>>...32