Scope of Inclusions. - Header files are made accessible to internal OS logic and to applications through include paths that are provided to the C/C++ compiler. + Header files are made accessible to internal OS logic and to applications through symbolic links and through include paths that are provided to the C/C++ compiler. Through these include paths, the NuttX build system also enforces modularity in the design. For example, one important design principle is architectural layering. In this case I am referring to the OS as layered in to application interface, common internal OS logic, and lower level platform-specific layers. @@ -1585,7 +1585,7 @@ The specific environmental definitions are unique for each board but should incl
Keeping in the spirit of the layered architecture, this publicly visible header files must not export platform-specific definitions; Only standardized definitions should be visible such as those provided in include/nuttx/arch.h or include/nuttx/board.h.
And, similarly, these publicly visible header file must not include files that reside in the inaccessible platform-specific source directories.
- That practice will cause inclusion failures when the publicly visiable file is included in common logic outside of the platform-specific source directories.
+ That practice will cause inclusion failures when the publicly visible file is included in common logic outside of the platform-specific source directories.