Searched refs:against (Results 1 – 25 of 1663) sorted by relevance
12345678910>>...67
36 # Build PDFium against Skia (experimental) rather than AGG. Use Skia to draw40 # Build PDFium against Skia (experimental) rather than AGG. Use Skia to draw59 # Don't build against bundled zlib.62 # Don't build against bundled lcms2.65 # Don't build against bundled libpng.
7 PURPOSE = "Ensure Chrome OS contains mitigations against CPU vulnerabilities."9 Passes when the kernel reports the appropriate mitigations against CPU19 This test ensures that the kernel contains appropriate mitigations against CPU
18 against LLVM.25 To link against the JIT:97 Print the flags needed to link against LLVM libraries.103 Print all the libraries needed to link against the specified LLVM111 without **-l** or pathnames. Useful for linking against a not-yet-installed
64 Notes for running POSIX Test Suite against Linux implementations of82 to build against LinuxThreads, add '-lpthread' to LDLIBS.88 Otherwise, to build against NPTL, export the following variable:98 To build against NGPT, export the following variables:115 To build against the posix1b message queues, see the semaphores information for posix1b.120 To build against the Michal Wronski/Krzysztof Benedyczak message queues,136 Otherwise, to build against NPTL, export the following variable:147 To run the semaphore test suite against posix1b, you will need to download
25 # R_PPC64_TOC16_DS against the .toc and the 'sin' external function33 # 1. A R_PPC64_ADDR64 against the .text segment plus addend (the function35 # 2. And a R_PPC64_TOC against no symbol (the linker will replace for the
15 against LLVM.19 To link against the JIT:67 Print the flags needed to link against LLVM libraries.71 Print all the libraries needed to link against the specified LLVM77 without B<-l> or pathnames. Useful for linking against a not-yet-installed
3 `test_that` is the supported mechanism to run autotests against Chrome OS18 In addition to running tests against local device, `test_that` can be used to19 launch jobs in the ChromeOS Hardware Lab (or against a local Autotest instance37 Run the smoke suite against dut:61 running tests against a specified host. The keyword :lab: is used as118 ### Running jobs against a local Autotest setup or MobLab120 `test_that` allows you to run jobs against a local Autotest setup or a
15 * A body of code to run tests against a remote device under test. In this21 `test_droid` for Android allow developers to run tests against a device27 capable of managing and running tests against thousands of devices in various29 scheduling of tests. Tests are run against this hardware daily to validate34 a work group interested in automated tests against a small set of devices.
39 // Components that directly use `NuggetClient` must link against it. Other40 // components should be written against `NuggetClientInterface` and can simply41 // link against `libnos`.
1 Although these could be executed against Linuxthreads, they are2 intended to test against the Native Posix Threading Library (NPTL).
3 Help: CA certificate to verify peer against19 If curl is built against the NSS SSL library, the NSS PEM PKCS#11 module22 (iOS and macOS only) If curl is built against Secure Transport, then this
13 this public key extraction requires libcurl to be linked against a copy of14 libssh2 1.2.8 or higher that is itself linked against OpenSSL.)
3 Help: CA directory to verify peer against9 built against OpenSSL, the directory must have been processed using the
28 To run the Clang static analyzer against a project goes like this:36 To run the Clang static analyzer against a project with compilation database62 The analyzer run against each modules after the build finished.66 The analyzer run against each modules after the build finished.90 compilation database. `analyze-build` does only run the analyzer against the
13 ## Failed to resolve libgtest.so.0 in tests when built against installed Google Test ##15 …u manually built and installed Google Test, and then built a Google Mock against it (either explic…19 …r the "sudo make install" for Google Test before any binaries which link against it can be execute…
10 to be easy to run against any Protocol Buffers implementation.22 Then to run the tests against the C++ implementation, run:31 To run these tests against a new Protocol Buffers implementation, write a
74 …rieves data back from output buffer to host memory. The data is compared against the expected outp…76 against expected output from compute shader. For parts that correspond to gaps, the data is random …93 …rieves data back from output buffer to host memory. The data is compared against the expected outp…95 against expected output from compute shader. For parts that correspond to gaps, the data is random …106 …rieves data back from output buffer to host memory. The data is compared against the expected outp…122 …rieves data back from output buffer to host memory. The data is compared against the expected outp…141 compared against the expected output from compute shader. On the other hand for each mipmap level t…142 against data stored in the input buffer (the compute shader could not have changed this data). The …157 …sparse images back to the CPU. Contents of the texels image are compared against the data original…158 …age that do not have backing device memory, the fetched data is compared against zeroed memory if …
4 Comparing against other serialization solutions, running on Windows 79 We also compare against code that doesn't use a serialization library15 We compare against Flatbuffers with the binary wire format (as36 ### Some other serialization systems we compared against but did not benchmark (yet), in rough orde…
18 Match against original/reply source/destination address27 Match against original/reply source/destination port (TCP/UDP/etc.) or GRE key.28 Matching against port ranges is only supported in kernel versions above 2.6.38.35 Match remaining lifetime in seconds against given value or range of values
69 dnl This tests against bugs in AIX 5.1, AIX 6.1..7.1, HP-UX 11.11,82 /* Test against AIX 5.1 bug: Failures are not distinguishable from successful102 /* Test against Solaris 10 bug: Failures are not distinguishable from122 /* Test against AIX 6.1..7.1 bug: Buffer overrun. */142 /* Test against HP-UX 11.11 bug: Positive return value instead of 0. */162 /* Test against HP-UX 11.11 bug: No converter from EUC-JP to UTF-8 is
4 # Previously .secrel32 and .secidx relocations against undefined symbols6 # resolving these relocations against symbols in other object files. Such
38 Programs such as fsck which didn't need to be linked against39 libext2fs (or mke2fs which didn't need to be linked against libe2p)40 only link against libraries they actually need. Otherwise, those
47 against = get_against() variable77 git('diff-index', '--check', '--cached', against, stderr=None)