Searched refs:against (Results 1 – 25 of 903) sorted by relevance
12345678910>>...37
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
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
23 ### Running tests against a single local device under test25 against a DUT connected directly to your workstation via a USB cable. Please39 against a given DUT:79 ### Running tests against a remote device under test80 `test_droid` can run tests against devices connected to a remote server. This
3 `test_that` is the supported mechanism to run autotests against Chrome OS32 Run the smoke suite against dut:56 running tests against a specified host. The keyword :lab: is used as
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
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
47 against a static value, while in "relative mode", two rate estimators are48 compared against another.69 Compare the estimator(s) by bytes or packets per second, and compare against
47 against = get_against() variable77 git('diff-index', '--check', '--cached', against, stderr=None)
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
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
45 # Regardless of whether the library ships against system freetype,46 # always link this binary against the bundled one for consistency
44 # Regardless of whether the library ships against system freetype,45 # always link this binary against the bundled one for consistency
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
14 # baseLocation - where things you are building against are installed15 # bootclasspath - The base jars to compile against (typicaly rt.jar)121 # against which you are building.122 # Base location for anything the build needs to compile against. For example,124 # installed Eclipse against which the application or plug-in code will be compiled and the RCP delt…177 # The location of the Java jars to compile against. Typically the rt.jar for your JDK/JRE180 # specific JRE locations to compile against. These values are used to compile bundles specifying a
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
7 PURPOSE = 'Group of WiFi tests that are run against a release candidate'8 CRITERIA = 'Run a set of tests against a given release candidate.'
26 \li Step 1: build your project against Eigen 3 with \ref Stage10 "Eigen 2 support stage 10". This m…27 \li Step 2: build your project against Eigen 3 with \ref Stage20 "Eigen 2 support stage 20". This m…28 \li Step 3: build your project against Eigen 3 with \ref Stage30 "Eigen 2 support stage 30". This m…29 \li Step 4: build your project against Eigen 3 with \ref Stage40 "Eigen 2 support stage 40". This m…30 \li Step 5: build your project against Eigen 3 without any Eigen 2 support mode.82 …migration as quickly as possible. While we do run the Eigen 2 test suite against Eigen 3's stage 1…
3 patch against Bouncy Castle's bcprov:38 patch against Bouncy Castle's bcpkix:
72 …rieves data back from output buffer to host memory. The data is compared against the expected outp…74 against expected output from compute shader. For parts that correspond to gaps, the data is random …91 …rieves data back from output buffer to host memory. The data is compared against the expected outp…93 against expected output from compute shader. For parts that correspond to gaps, the data is random …104 …rieves data back from output buffer to host memory. The data is compared against the expected outp…120 …rieves data back from output buffer to host memory. The data is compared against the expected outp…
2 # This should be possible to remove, if/when we build against
81 - link against -lunwind88 - link against -lunwind-$ARCH91 same application can be linked against the separate unwind libraries95 entire application would have to be linked against both -lunwind and
50 vertex or fragment color. Rendered image is compared against a53 Matrix constructor and coversion tests compare results against
1 # Anything that must be linked against the shared C library on Windows must9 # Build all configurations against shared C library