Lines Matching full:platforms

9 upstream Pigweed for non-host platforms:
22 See :ref:`docs-bazel-compatibility-background` and the `Platforms documentation
23 <https://bazel.build/extending/platforms>`_ for more context.
130 algorithmic, downstream users' platforms would become needlessly verbose. For
147 `platforms repo <https://github.com/bazelbuild/platforms>`_:
153      target_compatible_with = ["@platforms//os:linux"],
158 Some build targets are only intended for use on platforms with a fully-featured
184 `platforms repo <https://github.com/bazelbuild/platforms>`_:
192        "@platforms//cpu:armv6-m": [],
193        "@platforms//cpu:armv7-m": [],
194        "@platforms//cpu:armv7e-m": [],
195        "@platforms//cpu:armv7e-mf": [],
196        "@platforms//cpu:armv8-m": [],
259 Usage in platforms
294 Some modules may require platforms to explicitly assert that they support them,
295 but also work on host platforms by default. An example of this is
309      # Compatible with host platforms, and any platform that explicitly
375        "@platforms//os:macos": ":macos_backend",
376        "@platforms//os:linux": ":linux_backend",
377        "@platforms//os:windows": ":windows_backend",
483 Platforms can declare whether threads are joinable or not by including the
488    # //platforms/BUILD.bazel
504      # This library will be incompatible with "//platforms:my_device", on
564        target_compatible_with = ["@platforms//:incompatible"],
616 any constraints on its platform or not. This implied downstream platforms that
635 ``constraint_values`` explicitly in their platforms. A ``config_setting`` is
653        "//conditions:default": ["@platforms//:incompatible"],
747 that's ``@platforms//:incompatible``.
783 Platforms should explicitly set the backends of all facades they use via
803 #. `b/342691352  <https://pwbug.dev/342691352>`_ | "Platforms should set
829 provides explicit support for a number of specific hardware platforms, such as
831 <target-stm32f429i-disc1-stm32cube>`. For these specific platforms, every
851 <https://bazel.build/extending/platforms#skipping-incompatible-targets>`_.
856 not compatible with certain platforms. This is done through the
860 <https://bazel.build/reference/be/platforms-and-toolchains#constraint_value>`_
868      target_compatible_with = ["@platforms//os:linux"],
877 two sets of canonical ``constraint_values``, ``@platforms//os`` and
878 ``@platforms//cpu``.  Here are some possible choices---not necessarily good
916   platforms.
920   --platforms=@platforms//host //...`` works. This is necessary internally (for