diff options
Diffstat (limited to 'documentation/bsp-guide')
-rw-r--r-- | documentation/bsp-guide/bsp.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst index ab8ed54807..8ec7f2957e 100644 --- a/documentation/bsp-guide/bsp.rst +++ b/documentation/bsp-guide/bsp.rst | |||
@@ -1113,7 +1113,7 @@ list describes them in order of preference: | |||
1113 | #. *Use the LICENSE_FLAGS Variable to Define the Recipes that Have Commercial or | 1113 | #. *Use the LICENSE_FLAGS Variable to Define the Recipes that Have Commercial or |
1114 | Other Types of Specially-Licensed Packages:* For each of those recipes, you can | 1114 | Other Types of Specially-Licensed Packages:* For each of those recipes, you can |
1115 | specify a matching license string in a ``local.conf`` variable named | 1115 | specify a matching license string in a ``local.conf`` variable named |
1116 | :term:`LICENSE_FLAGS_WHITELIST`. | 1116 | :term:`LICENSE_FLAGS_ACCEPTED`. |
1117 | Specifying the matching license string signifies that you agree to | 1117 | Specifying the matching license string signifies that you agree to |
1118 | the license. Thus, the build system can build the corresponding | 1118 | the license. Thus, the build system can build the corresponding |
1119 | recipe and include the component in the image. See the | 1119 | recipe and include the component in the image. See the |
@@ -1122,15 +1122,15 @@ list describes them in order of preference: | |||
1122 | how to use these variables. | 1122 | how to use these variables. |
1123 | 1123 | ||
1124 | If you build as you normally would, without specifying any recipes in | 1124 | If you build as you normally would, without specifying any recipes in |
1125 | the :term:`LICENSE_FLAGS_WHITELIST` variable, the build stops and provides | 1125 | the :term:`LICENSE_FLAGS_ACCEPTED` variable, the build stops and provides |
1126 | you with the list of recipes that you have tried to include in the image | 1126 | you with the list of recipes that you have tried to include in the image |
1127 | that need entries in the :term:`LICENSE_FLAGS_WHITELIST` variable. Once you | 1127 | that need entries in the :term:`LICENSE_FLAGS_ACCEPTED` variable. Once you |
1128 | enter the appropriate license flags into it, restart the build to continue | 1128 | enter the appropriate license flags into it, restart the build to continue |
1129 | where it left off. During the build, the prompt will not appear again since | 1129 | where it left off. During the build, the prompt will not appear again since |
1130 | you have satisfied the requirement. | 1130 | you have satisfied the requirement. |
1131 | 1131 | ||
1132 | Once the appropriate license flags are on the white list in the | 1132 | Once the appropriate license flags are on the white list in the |
1133 | :term:`LICENSE_FLAGS_WHITELIST` variable, you can build the encumbered | 1133 | :term:`LICENSE_FLAGS_ACCEPTED` variable, you can build the encumbered |
1134 | image with no change at all to the normal build process. | 1134 | image with no change at all to the normal build process. |
1135 | 1135 | ||
1136 | #. *Get a Pre-Built Version of the BSP:* You can get this type of BSP by | 1136 | #. *Get a Pre-Built Version of the BSP:* You can get this type of BSP by |
@@ -1143,7 +1143,7 @@ list describes them in order of preference: | |||
1143 | click-through license agreements presented by the website. If you | 1143 | click-through license agreements presented by the website. If you |
1144 | want to build the image yourself using the recipes contained within | 1144 | want to build the image yourself using the recipes contained within |
1145 | the BSP tarball, you will still need to create an appropriate | 1145 | the BSP tarball, you will still need to create an appropriate |
1146 | :term:`LICENSE_FLAGS_WHITELIST` to match the encumbered recipes in the | 1146 | :term:`LICENSE_FLAGS_ACCEPTED` to match the encumbered recipes in the |
1147 | BSP. | 1147 | BSP. |
1148 | 1148 | ||
1149 | .. note:: | 1149 | .. note:: |