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