Lines Matching full:gn
4 Python GN Templates
9 The Python build is implemented with GN templates defined in
15 GN is built.
16 - The :bdg-ref-primary-line:`module-pw_build` docs for other GN templates
47 GN permits using abbreviated labels when the target name matches the directory
58 Pylint) are done within a single GN toolchain to avoid duplication in
60 ``pw_build_PYTHON_TOOLCHAIN`` GN arg, which defaults to
68 ``pw_build_TEST_TRANSITIVE_PYTHON_DEPS = false`` to your project's ``.gn``
97 It is best to keep these files within the same folder as the ``BUILD.gn``
118 - ``python_deps`` - Dependencies on other pw_python_packages in the GN build.
120 - ``other_deps`` - Dependencies on GN targets that are not pw_python_packages.
173 The ``pw_python_action`` template is a convenience wrapper around GN's `action
174 function <https://gn.googlesource.com/gn/+/main/docs/reference.md#func_action>`_
198 A Python script can be expressed in a single, concise GN target, rather than
246 https://cs.pigweed.dev/pigweed/+/main:pw_env_setup/BUILD.gn to create a
247 virtualenv for use within the GN build that all Python actions will run in.
253 :octicon:`file;1em` ``BUILD.gn``
281 to the GN root and must begin with "$root_build_dir/" if it lives in the
286 ``pw_build_PIP_CONSTRAINTS`` GN arg.
289 on creation. By default this is set to the ``pw_build_PIP_REQUIREMENTS`` GN
295 ``pw_build_PIP_REQUIREMENTS`` GN args see:
296 :ref:`docs-python-build-python-gn-requirements-files`
328 :octicon:`file;1em` ``BUILD.gn``
343 the ``pw_build_PIP_CONSTRAINTS`` GN arg.
369 GN build, like packages from PyPI, for example. Those should still be declared
384 `GN metadata
385 <https://gn.googlesource.com/gn/+/HEAD/docs/reference.md#var_metadata>`_ key,
395 any additional ``pw_python_package`` targets in the GN build they depend on,
396 directly or indirectly. Dependencies from outside the GN build, such as packages
460 - The source file should be a GN target label (starting with ``//``).
527 :caption: :octicon:`file;1em` ./pw_env_setup/BUILD.gn