Lines Matching refs:header

30   will be declared in some header under ``include/`` or in another
83 Any header file that declares system calls must include a special generated
84 header at the very bottom of the header file. This header follows the
85 naming convention ``syscalls/<name of header file>``. For example, at the
104 ``zephyr_syscall_header_ifdef`` are used to specify which header
106 present in the final binaries. Note that header files inside
142 C and header files by the :ref:`gen_syscalls.py` script, all of which can be found in
153     prototypes are declared in header files when
171 The body of the API is created in the generated system header. Using the
177 Inside this header is the body of :c:func:`k_sem_init()`::
244 declared in the same header as the API as a static inline function or
352 type.  This is defined in a header file that must be included from