!/tar/node_modules/minipass

!/text-table

!/tiny-relative-date

!/treeverse

!/tuf-js

!/tuf-js/node_modules/

{

}

{

}

You run the test driver with e.g.

``` sh

$ pip install --editable ".[dev]"

$ python -m pytest

Note that it can be handy to look at the project files output by the tests

to diagnose problems. The easiest way to do that is by kindly asking the

test driver to leave the temporary directories it creates in-place.

{

'include_dirs': ['include'], # Treated as relative to ../build

'defines': ['NDEBUG'], # defines does not contain pathnames

}

{

'sources': ['string_util.cc'],

'include_dirs': ['../build/include'],

'libraries': ['-lz'],

'defines': ['NDEBUG'],

}

| `all_dependent_settings` | A dictionary of settings to be applied to all dependents of the target, transitively. This includes direct dependents and the entire set of their dependents, and so on. This section may contain anything found within a `target` dictionary, except `configurations`, `target_name`, and `type` sections. Compare `direct_dependent_settings` and `link_settings`. |

| `configurations` | A list of dictionaries defining build configurations for the target. See the "Configurations" section below. |

| `copies` | A list of copy actions to perform. See the "Copies" section below. |

| `dependencies` | A list of targets on which this target depends. Targets in other `.gyp` files are specified as `../path/to/other.gyp:target_we_want`. |

| `direct_dependent_settings` | A dictionary of settings to be applied to other targets that depend on this target. These settings will only be applied to direct dependents. This section may contain anything found within a `target` dictionary, except `configurations`, `target_name`, and `type` sections. Compare with `all_dependent_settings` and `link_settings`. |

| `include_dirs` | A list of include directories to be passed on the command line to the C/C++ compiler (via `-I` or `/I` options). |

Conditionals may appear within any dictionary in a `.gyp` file. There

are two tpes of conditionals, which differ only in the timing of their

dependencies have been computed.

A conditional section is introduced with a `conditions` or

Verifies that the output string contains all of the "lines" in the specified

list of lines. In practice, the lines can be any substring and need not be

Verifies that the output string does _not_ contain any of the "lines" in the

specified list of lines. In practice, the lines can be any substring and need

the test fails.

Verifies that the output string contains at least one of the "lines" in the

specified list of lines. In practice, the lines can be any substring and need

the test fails.

`'conditions'`: A list of condition specifications that can modify the

contents of the items in the global dictionary defined by this `.gyp`

above example, the most common use of a `conditions` section in the

top-level dictionary is to add platform-specific targets to the

`targets` list.

already in the `conditions` for the target), and you can't change the

file name, there are two patterns that can be used.

dictionary within the `targets` list. Add an appropriate `conditions`

section to exclude the specific files name:

Adding a library often involves updating multiple `.gyp` files, adding

file), and updating targets in the other `.gyp` files that depend on

(link with) the new library.

`direct_dependent_settings` block.

Note that these settings will likely need to be replicated in the

with the same options. This does not prevent the target from defining

additional options for its "internal" use when compiling its own source

files. (In the above example, these are the `LOCAL_DEFINE_FOR_LIBBAR`

import os

import subprocess

def IsCygwin():