diff options
Diffstat (limited to 'pw_sys_io_stdio')
-rw-r--r-- | pw_sys_io_stdio/BUILD.bazel | 5 | ||||
-rw-r--r-- | pw_sys_io_stdio/docs.rst | 7 |
2 files changed, 8 insertions, 4 deletions
diff --git a/pw_sys_io_stdio/BUILD.bazel b/pw_sys_io_stdio/BUILD.bazel index 23d510387..381ce9810 100644 --- a/pw_sys_io_stdio/BUILD.bazel +++ b/pw_sys_io_stdio/BUILD.bazel @@ -25,6 +25,11 @@ package(default_visibility = ["//visibility:public"]) licenses(["notice"]) +constraint_value( + name = "backend", + constraint_setting = "//pw_sys_io:backend_constraint_setting", +) + pw_cc_library( name = "pw_sys_io_stdio", srcs = ["sys_io.cc"], diff --git a/pw_sys_io_stdio/docs.rst b/pw_sys_io_stdio/docs.rst index 728065624..eaa45af41 100644 --- a/pw_sys_io_stdio/docs.rst +++ b/pw_sys_io_stdio/docs.rst @@ -8,7 +8,6 @@ stdio. Why not just use stdio directly? -------------------------------- - The nice thing about using ``pw_sys_io`` is that it's rather easy to get a board up and running with a target-specific backend. This means when drafting out a quick application you can write it against ``pw_sys_io`` and, with some @@ -21,8 +20,8 @@ Setup ===== This module requires relatively minimal setup: - 1. Write code against the ``pw_sys_io`` facade. - 2. Direct the ``pw_sys_io_BACKEND`` GN build arg to point to this backend. +1. Write code against the ``pw_sys_io`` facade. +2. Direct the ``pw_sys_io_BACKEND`` GN build arg to point to this backend. Module usage ============ @@ -31,4 +30,4 @@ to an application built directly against stdio. Dependencies ============ - * ``pw_sys_io`` facade +- :ref:`module-pw_sys_io` |