Searched refs:against (Results 1 – 25 of 1072) sorted by relevance
12345678910>>...43
14 # baseLocation - where things you are building against are installed15 # bootclasspath - The base jars to compile against (typicaly rt.jar)66 # Base location for anything the build needs to compile against. For example,68 # installed Eclipse against which the GEF code will be compiled.76 #the os value of the Eclipse binary against which you are compiling81 #the ws value of the Eclipse binary against which you are compiling86 #the arch value of the Eclipse binary against which you are compiling108 # The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE
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
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.
1 Although these could be executed against Linuxthreads, they are2 intended to test against the Native Posix Threading Library (NPTL).
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
18 ### Running tests against a single local device under test20 against a DUT connected directly to your workstation via a USB cable. Please25 against a given DUT:80 ### Running tests against a remote device under test81 `test_droid` can run tests against devices connected to a remote server. This
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…
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 # Build PDFium against skia (experimental) rather than agg, replacing all PDFium graphics.16 # Build PDFium against skia (experimental) rather than agg, adding only path support.
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
14 # baseLocation - where things you are building against are installed15 # bootclasspath - The base jars to compile against (typicaly rt.jar)148 # against which you are building.149 # Base location for anything the build needs to compile against. For example,151 # installed Eclipse against which the application or plug-in code will be compiled and the RCP delt…156 #Folder containing repositories whose content is needed to compile against158 …ositories from ${repoBaseLocation} will be made available as a form suitable to be compiled against212 # The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE215 # specific JRE locations to compile against. These values are used to compile bundles specifying 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
47 against = get_against() variable77 git('diff-index', '--check', '--cached', against, stderr=None)
5 can use to test a variety of performance scenarios against your22 likely want to run several benchmarks against each data set (parse,
11 protobuf. The browser only links against the light version, so you will get13 and then try to use it in Chrome. Currently CrOS links against the full
11 SafeStack is an instrumentation pass that protects programs against attacks73 region. The safe stack is automatically protected against stack-based buffer76 is protected against arbitrary memory write vulnerabilities though84 A complete protection against control-flow hijack attacks requires combining96 In its current implementation, SafeStack provides precise protection against97 stack-based buffer overflows, but protection against arbitrary memory write157 stack. The safe stack remains unprotected against memory errors when accessing
49 ** Make it possible to link against libunwind-ia64.a only (i.e., without53 ** Dont link against libatomic_ops for now. Due to a packaging bug on54 Debian, linking against this library causes libunwind.so to get56 Fortunately, we don't have to link against that library on x86 or59 we can re-enable linking against libatomic_ops.69 fixed in the 0.98.2 release by explicitly linking against libgcc.a156 programs linked against libunwind v0.97 won't be
16 # baseLocation - where things you are building against are installed17 # bootclasspath - The base jars to compile against (typicaly rt.jar)123 # against which you are building.124 # Base location for anything the build needs to compile against. For example,126 # installed Eclipse against which the application or plug-in code will be compiled and the RCP delt…179 # The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE182 # specific JRE locations to compile against. These values are used to compile bundles specifying a