diff options
Diffstat (limited to 'documentation/transitioning-to-a-custom-environment.rst')
-rw-r--r-- | documentation/transitioning-to-a-custom-environment.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/transitioning-to-a-custom-environment.rst b/documentation/transitioning-to-a-custom-environment.rst index 6b34fedc269..6ff55e56191 100644 --- a/documentation/transitioning-to-a-custom-environment.rst +++ b/documentation/transitioning-to-a-custom-environment.rst @@ -42,7 +42,7 @@ Transitioning to a custom environment for systems development You might want to start with the build specification that Poky provides (which is reference embedded distribution) and then add your newly chosen layers to that. Here is the information :ref:`about adding layers - <dev-manual/common-tasks:Understanding and Creating Layers>`. + <dev-manual/layers:Understanding and Creating Layers>`. #. **Based on the layers you've chosen, make needed changes in your configuration**. @@ -58,7 +58,7 @@ Transitioning to a custom environment for systems development releases. If you are using a Yocto Project release earlier than 2.4, use the ``yocto-layer create`` tool. The ``bitbake-layers`` tool also provides a number of other useful layer-related commands. See - :ref:`dev-manual/common-tasks:creating a general layer using the + :ref:`dev-manual/layers:creating a general layer using the \`\`bitbake-layers\`\` script` section. #. **Create your own layer for the BSP you're going to use**. @@ -79,12 +79,12 @@ Transitioning to a custom environment for systems development process of refinement. Start by getting each step of the build process working beginning with fetching all the way through packaging. Next, run the software on your target and refine further as needed. See :ref:`Writing a New - Recipe <dev-manual/common-tasks:writing a new recipe>` in the + Recipe <dev-manual/new-recipe:writing a new recipe>` in the Yocto Project Development Tasks Manual for more information. #. **Now you're ready to create an image recipe**. There are a number of ways to do this. However, it is strongly recommended - that you have your own image recipe - don't try appending to existing image + that you have your own image recipe --- don't try appending to existing image recipes. Recipes for images are trivial to create and you usually want to fully customize their contents. @@ -103,7 +103,7 @@ Transitioning to a custom environment for systems development needs to change for your distribution. If you find yourself adding a lot of configuration to your local.conf file aside from paths and other typical local settings, it's time to :ref:`consider creating your own distribution - <dev-manual/common-tasks:creating your own distribution>`. + <dev-manual/custom-distribution:creating your own distribution>`. You can add product specifications that can customize the distribution if needed in other layers. You can also add other functionality specific to the |