2020-10-01 01:59:33 +00:00
|
|
|
.. _module-pw_sys_io_stdio:
|
2019-12-06 21:06:01 +00:00
|
|
|
|
2020-03-02 22:58:59 +00:00
|
|
|
---------------
|
|
|
|
pw_sys_io_stdio
|
|
|
|
---------------
|
|
|
|
The ``pw_sys_io_stdio`` backend implements the ``pw_sys_io`` facade using
|
2019-12-06 21:06:01 +00:00
|
|
|
stdio.
|
|
|
|
|
|
|
|
Why not just use stdio directly?
|
|
|
|
--------------------------------
|
|
|
|
|
2020-03-02 22:58:59 +00:00
|
|
|
The nice thing about using ``pw_sys_io`` is that it's rather easy to get a
|
2019-12-06 21:06:01 +00:00
|
|
|
board up and running with a target-specific backend. This means when drafting
|
2020-03-02 22:58:59 +00:00
|
|
|
out a quick application you can write it against ``pw_sys_io`` and, with some
|
2019-12-06 21:06:01 +00:00
|
|
|
care, the application will be able to run on both host and target devices.
|
|
|
|
|
2020-03-02 22:58:59 +00:00
|
|
|
While it's not recommended to use ``pw_sys_io`` for any production
|
2019-12-06 21:06:01 +00:00
|
|
|
applications, it can be rather helpful for early prototyping.
|
|
|
|
|
|
|
|
Setup
|
|
|
|
=====
|
|
|
|
This module requires relatively minimal setup:
|
|
|
|
|
2020-03-02 22:58:59 +00:00
|
|
|
1. Write code against the ``pw_sys_io`` facade.
|
2020-06-15 23:30:40 +00:00
|
|
|
2. Direct the ``pw_sys_io_BACKEND`` GN build arg to point to this backend.
|
2019-12-06 21:06:01 +00:00
|
|
|
|
|
|
|
Module usage
|
|
|
|
============
|
|
|
|
For the most part, applications built with this backend will behave similarly
|
|
|
|
to an application built directly against stdio.
|
|
|
|
|
|
|
|
Dependencies
|
|
|
|
============
|
2020-03-13 20:06:24 +00:00
|
|
|
* ``pw_sys_io`` facade
|