blob: 31a9357e15034ef87494029c116d1973beadd6a3 [file] [log] [blame]
Armando Montanezf7a5a742020-03-02 14:58:59 -08001.. _chapter-pw-sys-io-stdio:
2
3.. default-domain:: cpp
4
5.. highlight:: sh
6
7---------------
8pw_sys_io_stdio
9---------------
10The ``pw_sys_io_stdio`` backend implements the ``pw_sys_io`` facade using
11stdio.
12
13Why not just use stdio directly?
14--------------------------------
15
16The nice thing about using ``pw_sys_io`` is that it's rather easy to get a
17board up and running with a target-specific backend. This means when drafting
18out a quick application you can write it against ``pw_sys_io`` and, with some
19care, the application will be able to run on both host and target devices.
20
21While it's not recommended to use ``pw_sys_io`` for any production
22applications, it can be rather helpful for early prototyping.
23
24Setup
25=====
26This module requires relatively minimal setup:
27
28 1. Write code against the ``pw_sys_io`` facade.
Armando Montaneza761e322020-06-15 16:30:40 -070029 2. Direct the ``pw_sys_io_BACKEND`` GN build arg to point to this backend.
Armando Montanezf7a5a742020-03-02 14:58:59 -080030
31Module usage
32============
33For the most part, applications built with this backend will behave similarly
34to an application built directly against stdio.
35
36Dependencies
37============
Armando Montanez0054a9b2020-03-13 13:06:24 -070038 * ``pw_sys_io`` facade