tinnedkarma commented on code in PR #17162:
URL: https://github.com/apache/nuttx/pull/17162#discussion_r2527927853


##########
Documentation/implementation/make_build_system.rst:
##########
@@ -0,0 +1,603 @@
+=================
+Make Build System
+=================
+
+Currently, NuttX supports both CMake and Make build systems.
+This guide explains the NuttX `make`-based build system.
+
+Due to *requirements, constraints, and the complexity of the build process*, 
NuttX divides
+this work into multiple files, each handling specific parts of the build 
process.
+
+As stated in :doc:`/introduction/inviolables`, multiple platforms should be 
supported:
+
+- :ref:`win_mk`: handles windows platform support.
+- :ref:`unix_mk`: handles unix-like platforms support.
+
+NuttX supports multiple build modes. See :doc:`/guides/protected_build`:
+
+- :ref:`flatlibs_mk`: Kernel and user-space built into a single `blob`.
+- :ref:`protectedlibs_mk`: Kernel and user-space built as two separate `blobs`.
+- :ref:`kernelibs_mk`: Kernel built into single `blob`. User apps must be 
loaded
+  into memory for execution.
+
+NuttX targets multiple libs, or `silos`, each handling its own compilation:
+
+.. note::
+
+  Gregory Nutt has a nice presentation about
+  `NuttX architecture 
<https://cwiki.apache.org/confluence/pages/viewpage.action?
+  pageId=139629399&preview=/139629402/140774623/nuttx-3-archoverview.pdf>`_
+
+  There the `silo` concept is explained. Only the `silos` there are listed 
below as libs.

Review Comment:
   I just looked up, you are indeed right. 
   Backquotes around text defines interpreted text. The default behavior of 
interpreted text is `:title-reference:` which is the same as `:emphasis:`. 
   The default role can be changed using `.. default-role::`.
   This is why I though they were the same, on the project I am currently 
working on they changed the default role. o.O



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to