/external/chromium_org/native_client_sdk/src/tools/ |
create_nmf.py | 9 any shared libraries dependencies that the executables might have. 189 staging the libraries and for inclusion into the nmf file. 192 no_arch_prefix: Don't prefix shared libraries by lib32/lib64. 518 # Core toolchain libraries 521 # naclports installed libraries 524 # SDK bundle libraries 527 # naclports bundle libraries 567 help='A path to prepend to shared libraries in the .nmf', 573 help='Destination directory for staging libraries', 576 help='Don\'t put shared libraries in the lib32/lib64 [all...] |
/external/lldb/www/ |
symbolication.html | 36 that we don't load all of the dependent shared libraries from the current
39 reference shared libraries in "/usr/lib", we often don't want to load
41 <p>Using the "image list" command will show us a list of all shared libraries
60 have loaded all dependent shared libraries:<p>
72 matches since most shared libraries have a virtual address space that starts at zero:</p>
138 or one of the shared libraries, then add more modules to the target using the
148 <p>First we create the target using the main executable and then add any extra shared libraries we want:</p>
223 will recreate the target and add the three shared libraries that we added in the darwin
279 100 to 200 different shared libraries loaded, but your crash log stack backtraces only use a few
280 of these shared libraries. Only the images that contain stack backtrace addresses need to be loaded [all...] |
/development/ndk/platforms/ |
README.CRT.TXT | 31 executable (possibly loading any dependent system libraries as well), 36 shared libraries. One major difference is that there is no _start 68 or during 'dlopen()' for shared libraries (either implicit or explicit). 75 or during 'dlclose()' for shared libraries (either implicit or explicit). 163 that shall *not* be exported by the NDK-provided link-time libraries (i.e. 176 None of the link-time NDK shared libraries should export any libgcc symbol. 183 libgcc symbol from the link-time shared libraries it generates. This is done
|
/external/chromium_org/third_party/skia/third_party/lua/doc/ |
readme.html | 101 an easy-to-use distribution of Lua that includes many useful libraries. 248 create and use libraries with your compiler. Moreover, to dynamically load 249 C libraries for Lua you'll need to know how to create dynamic libraries 251 those dynamic libraries — but <EM>don't</EM> link the Lua library 296 <H3>Libraries</H3> 301 <LI> <CODE>loadlib</CODE> may load libraries with global names (RTLD_GLOBAL)
|
/external/e2fsprogs/config/ |
config.rpath | 3 # run time search path of shared libraries in an executable. 120 # that the semantics of dynamic libraries on AmigaOS, at least up 123 # behavior of shared libraries on other platforms, we can use 380 sys_lib_search_path_spec=`$CC -print-search-dirs | grep "^libraries:" | sed -e "s/^libraries://" -e "s/;/ /g"` 507 # Compile-time system search path for libraries 510 # Run-time system search path for libraries
|
/external/owasp/sanitizer/tools/findbugs/doc/ |
AddingDetectors.txt | 206 7. Using 3rd party libraries in the detector 210 libraries during the analysis. This libraries must be part of standard jar class path 228 and specify there locations of any additional plugin libraries. 231 may extend the default FindBugs classpath and use custom libraries during the analysis. 232 This libraries must be part of standard Eclipse plugin dependencies specified via 234 In case custom detectors need access to this custom libraries at runtime, an
|
/external/protobuf/gtest/scons/ |
SConscript | 43 libraries are copied to the folder indicated by the variable. 145 """Builds static libraries for gtest and gtest_main in build_env. 148 build_env: An environment in which to build libraries. 170 gtest_libs: The gtest library or the list of libraries to link. 195 gtest_libs: The gtest library or the list of libraries to use. 209 gtest_libs: The gtest library or the list of libraries to use. 228 # Install the libraries if needed.
|
/ndk/build/tools/ |
builder-funcs.sh | 17 # used to either build a static and shared libraries from sources, or 378 # Important: -lgcc must appear after objects and static libraries, 379 # but before shared libraries for Android. It doesn't hurt 444 # Important: -lgcc must appear after objects and static libraries, 445 # but before shared libraries for Android. It doesn't hurt 472 # Important: -lgcc must appear after objects and static libraries, 473 # but before shared libraries for Android. It doesn't hurt
|
DEV-SCRIPTS-USAGE.TXT | 37 Contains sources of various libraries or programs that will be 43 Contains the sources of various C++ runtime and libraries that 50 libraries from these sources, that will be copied under this 56 libraries from these sources, that will be copied under this directory. 61 prebuilt libraries from these sources, that will be copied under this 67 libraries from the sources that are located in the toolchain source 88 libraries used with 'ndk-build'. For example, the 'cpu-features' 132 Contains several CPU-specific object files and static libraries that 135 Before NDK r7, this also contains prebuilt system shared libraries that 148 shared libraries that can be used by ndk-build at link time. The shel [all...] |
/ndk/docs/text/ |
CPLUSPLUS-SUPPORT.text | 36 your code will depend on. It is not possible to mix shared libraries compiled 97 Available as both both static and shared libraries. To use it, use either 182 On the other hand, if you have two shared libraries in your project 217 You will need to load the libraries in reverse dependency order, as in: 238 This NDK provides prebuilt static and shared libraries for STLport, 268 as/ld/headers/libraries so they get -latomic too. The version of libatomic in gcc4.8 271 This NDK provides prebuilt static and shared libraries for libc++
|
CPU-ARCH-ABIS.text | 19 - the format of executable binaries (shared libraries, programs, etc...) 30 generally from a very specific selected set of libraries. 286 each ABI listed on this line. Both libraries will be copied to your application 299 will ensure that your application package contains libraries for all target ABIs. 301 its own set of native libraries built from the same sources. 315 It is expected that shared libraries generated with the NDK are stored in 331 to verify that the native shared libraries you want are indeed at the 332 proper location. You can also place native shared libraries at other 337 In the case of a "fat" binary, up to four distinct libraries can be placed 394 then scan for shared libraries of the form [all...] |
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/distutils/ |
bcppcompiler.py | 176 libraries=None, 190 (libraries, library_dirs, runtime_library_dirs) = \ 191 self._fix_lib_args (libraries, library_dirs, runtime_library_dirs) 264 # no map file and start libraries 267 for lib in libraries: 278 # some default libraries 317 # seems to have a different format for static libraries.
|
/prebuilts/python/linux-x86/2.7.5/lib/python2.7/distutils/ |
bcppcompiler.py | 176 libraries=None, 190 (libraries, library_dirs, runtime_library_dirs) = \ 191 self._fix_lib_args (libraries, library_dirs, runtime_library_dirs) 264 # no map file and start libraries 267 for lib in libraries: 278 # some default libraries 317 # seems to have a different format for static libraries.
|
/prebuilts/gcc/linux-x86/host/x86_64-w64-mingw32-4.8/share/man/man1/ |
x86_64-w64-mingw32-ld.1 | 151 This version of \fBld\fR uses the general purpose \s-1BFD\s0 libraries 286 finds an object with an audit entry while searching for shared libraries, 318 supported by the \s-1BFD\s0 libraries. (You can list the available binary 384 Specifies a list of archive libraries from which symbols should not be automatically 386 \&\f(CW\*(C`\-\-exclude\-libs ALL\*(C'\fR excludes symbols in all archive libraries from 542 On systems which support shared libraries, \fBld\fR may also search for 573 for archive libraries and \fBld\fR control scripts. You may use this 656 libraries. If the output format supports Unix style magic numbers, 666 libraries. If the output format supports Unix style magic numbers, 675 shared libraries. Use \fB\-Bdynamic\fR for this [all...] |
/external/llvm/docs/ |
GettingStarted.rst | 15 contains all of the tools, libraries, and header files needed to use LLVM. It 73 where you want the LLVM tools and libraries to be installed (default 143 information and the fact that the libraries are statically linked into multiple 208 * **ranlib** --- symbol table builder for archive libraries 391 locations of your bitcode libraries. It is provided only as a convenience 409 Source release for the LLVM libraries and tools. 689 Enables debug symbols in the runtime libraries. The default is to strip debug 690 symbols from the runtime libraries. 747 configuration). The build system will compile the tools and libraries with 755 line. For these builds, the build system will compile the tools and libraries [all...] |
/external/chromium_org/third_party/icu/ |
readme.html | 97 Unicode (ICU) libraries provide robust and full-featured Unicode services on 98 a wide variety of platforms to help this design goal. The ICU libraries 271 Design</a> section of the User's Guide to see which libraries you need for 273 and the common (<code>[lib]icuuc</code>) libraries in order to use ICU.</p> 499 <td>Contains the import libraries for linking ICU into your Windows 506 <td>Contains the libraries and executables for using ICU on Windows.</td> 550 and statically linked ICU libraries become smaller. 600 <li><b>Static libraries:</b> It may make sense to build the ICU code 601 into static libraries (.a) rather than shared libraries (.so/.dll) [all...] |
/external/icu/icu4c/ |
readme.html | 104 Unicode (ICU) libraries provide robust and full-featured Unicode services on 105 a wide variety of platforms to help this design goal. The ICU libraries 288 Design</a> section of the User's Guide to see which libraries you need for 290 and the common (<code>[lib]icuuc</code>) libraries in order to use ICU.</p> 516 <td>Contains the import libraries for linking ICU into your Windows 523 <td>Contains the libraries and executables for using ICU on Windows.</td> 567 and statically linked ICU libraries become smaller. 647 <li><b>Static libraries:</b> It may make sense to build the ICU code 648 into static libraries (.a) rather than shared libraries (.so/.dll) [all...] |
/external/ltrace/ |
ltrace.1 | 96 libraries\fR--see ltrace.conf(5) for details on the syntax of these 98 \fBltrace\fR finds prototype libraries. 137 directory, that directory is considered when prototype libraries are 140 libraries. 146 Display only calls to functions implemented by libraries that match 153 the selected libraries, there's no actual guarantee that the call 213 used to pick symbols for tracing from libraries that the process uses. 240 In libraries that don't have an explicit SONAME, basename is taken for 275 called prototype libraries. 285 prototype is looked up in all prototype libraries loaded for give [all...] |
/external/chromium_org/third_party/WebKit/Source/core/ |
LICENSE-LGPL-2 | 21 other libraries whose authors decide to use it. You can use it for 22 your libraries, too. 63 Most GNU software, including some libraries, is covered by the ordinary 66 designated libraries. This license is quite different from the ordinary 70 The reason we have a separate public license for some libraries is that 80 Public License for libraries did not effectively promote software 81 sharing, because most developers did not use the libraries. We 86 libraries themselves. This Library General Public License is intended to 87 permit developers of non-free programs to use free libraries, while 89 libraries that are incorporated in them. (We have not seen how to achiev [all...] |
/external/chromium_org/third_party/gtk+/ |
COPYING | 21 other libraries whose authors decide to use it. You can use it for 22 your libraries, too. 63 Most GNU software, including some libraries, is covered by the ordinary 66 designated libraries. This license is quite different from the ordinary 70 The reason we have a separate public license for some libraries is that 80 Public License for libraries did not effectively promote software 81 sharing, because most developers did not use the libraries. We 86 libraries themselves. This Library General Public License is intended to 87 permit developers of non-free programs to use free libraries, while 89 libraries that are incorporated in them. (We have not seen how to achiev [all...] |
/external/chromium_org/third_party/mesa/ |
LICENSE | 51 other libraries whose authors decide to use it. You can use it for 52 your libraries, too. 93 Most GNU software, including some libraries, is covered by the ordinary 96 designated libraries. This license is quite different from the ordinary 100 The reason we have a separate public license for some libraries is that 110 Public License for libraries did not effectively promote software 111 sharing, because most developers did not use the libraries. We 116 libraries themselves. This Library General Public License is intended to 117 permit developers of non-free programs to use free libraries, while 119 libraries that are incorporated in them. (We have not seen how to achiev [all...] |
/external/chromium_org/third_party/mesa/src/docs/ |
COPYING | 29 other libraries whose authors decide to use it. You can use it for 30 your libraries, too. 71 Most GNU software, including some libraries, is covered by the ordinary 74 designated libraries. This license is quite different from the ordinary 78 The reason we have a separate public license for some libraries is that 88 Public License for libraries did not effectively promote software 89 sharing, because most developers did not use the libraries. We 94 libraries themselves. This Library General Public License is intended to 95 permit developers of non-free programs to use free libraries, while 97 libraries that are incorporated in them. (We have not seen how to achiev [all...] |
/external/chromium_org/third_party/yasm/source/patched-yasm/ |
GNU_LGPL-2.0 | 21 other libraries whose authors decide to use it. You can use it for 22 your libraries, too. 63 Most GNU software, including some libraries, is covered by the ordinary 66 designated libraries. This license is quite different from the ordinary 70 The reason we have a separate public license for some libraries is that 80 Public License for libraries did not effectively promote software 81 sharing, because most developers did not use the libraries. We 86 libraries themselves. This Library General Public License is intended to 87 permit developers of non-free programs to use free libraries, while 89 libraries that are incorporated in them. (We have not seen how to achiev [all...] |
/external/mesa3d/docs/ |
COPYING | 29 other libraries whose authors decide to use it. You can use it for 30 your libraries, too. 71 Most GNU software, including some libraries, is covered by the ordinary 74 designated libraries. This license is quite different from the ordinary 78 The reason we have a separate public license for some libraries is that 88 Public License for libraries did not effectively promote software 89 sharing, because most developers did not use the libraries. We 94 libraries themselves. This Library General Public License is intended to 95 permit developers of non-free programs to use free libraries, while 97 libraries that are incorporated in them. (We have not seen how to achiev [all...] |
/ndk/sources/host-tools/make-3.81/glob/ |
COPYING.LIB | 21 other libraries whose authors decide to use it. You can use it for 22 your libraries, too. 63 Most GNU software, including some libraries, is covered by the ordinary 66 designated libraries. This license is quite different from the ordinary 70 The reason we have a separate public license for some libraries is that 80 Public License for libraries did not effectively promote software 81 sharing, because most developers did not use the libraries. We 86 libraries themselves. This Library General Public License is intended to 87 permit developers of non-free programs to use free libraries, while 89 libraries that are incorporated in them. (We have not seen how to achiev [all...] |