Lines Matching refs:recipe
204 - *devtool upgrade*: Updates an existing recipe so that you can
208 ``devtool``. When you use ``devtool add``, a recipe is automatically
209 created. When you use ``devtool modify``, the specified existing recipe
212 the recipe a source tree that is under your control is used in order to
222 The ``devtool add`` command generates a new recipe based on existing
239 scenarios by which you could use ``devtool add`` to generate a recipe
246 access to the code, a recipe, and a controlled area in which to do
259 $ devtool add recipe fetchuri
263 folder. The command then creates a recipe named recipe and a
265 recipe, the command makes an attempt to determine the recipe name.
283 $ devtool add recipe srctree fetchuri
289 Within workspace, ``devtool`` creates a recipe named recipe along
296 The following command provides a new recipe name and identifies
299 $ devtool add recipe srctree
301 The command examines the source code and creates a recipe named
302 recipe for the code and places the recipe into the workspace.
306 new recipe is placed in the workspace.
308 Aside from a recipe folder, the command also creates an associated
311 2. *Edit the Recipe*: You can use ``devtool edit-recipe`` to open up the
315 $ devtool edit-recipe recipe
318 can make modifications to the recipe that take effect when you build
328 $ devtool build recipe
330 On the other hand, if you want an image to contain the recipe's
338 to build out your recipe, you probably want to see if the resulting
351 ``devtool deploy-target`` command: $ devtool deploy-target recipe
361 repository, moves the new recipe to a more permanent layer, and then
362 resets the recipe so that the recipe is built normally rather than
366 $ devtool finish recipe layer
373 As mentioned, the ``devtool finish`` command moves the final recipe
378 can build the recipe from those areas rather than the workspace.
392 that already has a local recipe in place that is used to build the
394 from an upstream source, specify the existing recipe, and keep track of
410 - The recipe exists locally in a layer external to the ``devtool``
417 for use with the Yocto Project and their recipe already resides in
425 location. The recipe, in this scenario, is in its own layer
428 The following command identifies the recipe and, by default,
431 $ devtool modify recipe
434 ``devtool``\ locates the recipe, ``devtool`` uses the recipe's
445 append file within the workspace while the recipe remains in its
461 area as a Git repository. The recipe, in this scenario, is again
464 The following command tells ``devtool`` the recipe with which to
469 $ devtool modify recipe srctree
479 As with all extractions, the command uses the recipe's :term:`SRC_URI`
488 recipe. The recipe remains in its original location but the source
494 workspace. In this example, the recipe also exists elsewhere
497 The following command tells ``devtool`` the recipe with which to
502 $ devtool modify -n recipe srctree
507 command, any non-patch files that might exist next to the recipe
512 append file for the recipe in the ``devtool`` workspace. The
513 recipe and the source code remain in their original locations.
525 $ devtool build recipe
527 On the other hand, if you want an image to contain the recipe's
533 to build out your recipe, you probably want to see if the resulting
548 $ devtool deploy-target recipe target
559 repository, updates the recipe to point to them (or creates a
561 layer), and then resets the recipe so that the recipe is built
565 $ devtool finish recipe layer
574 Because there is no need to move the recipe, ``devtool finish``
575 either updates the original recipe in the original layer or the
578 preserved in the original files next to the recipe during the
583 can build the recipe from those areas rather than from the workspace.
596 The ``devtool upgrade`` command upgrades an existing recipe to that of a
629 - The recipe exists in a local layer external to the ``devtool``
634 in the recipe (e.g. a tarball with the new version number in the
638 revision so that it has been upgraded. The recipe you have access to
639 is likely in your own layer. Thus, you need to upgrade the recipe to
642 $ devtool upgrade -V version recipe
650 $ devtool upgrade -V version recipe srctree
655 don't use "-V", the command upgrades the recipe to the latest
659 recipe are in a Git repository, you must provide the "-S" option and
662 Once ``devtool`` locates the recipe, it uses the :term:`SRC_URI` variable
665 the new version of the recipe, and an append file all within the
679 if your recipe specifies some patch files in :term:`SRC_URI` that
694 $ devtool build recipe
696 On the other hand, if you want an image to contain the recipe's
704 or ``bitbake`` to build your recipe, you probably want to see if the
717 ``devtool deploy-target`` command: $ devtool deploy-target recipe
727 repository, moves the new recipe to a more permanent layer, and then
728 resets the recipe so that the recipe is built normally rather than
732 the original files next to the recipe during the ``devtool finish``
736 source, then the old version of the recipe and associated files are
740 $ devtool finish recipe layer
749 can build the recipe from those areas rather than the workspace.
762 The ``devtool add`` command automatically creates a recipe based on the
791 In most cases, you need to edit the automatically generated recipe in
793 several edit and build cycles until the recipe successfully builds.
794 Once the recipe builds, you could use possible further iterations to
795 test the recipe on the target device.
798 the recipe are generated.
807 created recipe file accordingly.
815 incorrect. For such a case, you must reset the recipe::
829 recipe. If a dependency cannot be mapped, ``devtool`` places a comment
830 in the recipe indicating such. The inability to map a dependency can
833 must use the ``devtool add`` command to add an additional recipe that
834 satisfies the dependency. Once you add that recipe, you need to update
835 the :term:`DEPENDS` variable in the original recipe to include the new
836 recipe.
839 following to your recipe::
850 configure script for the software the recipe is building for further
875 correct licensing should you upgrade the recipe to a newer upstream
900 When writing a recipe for Makefile-only software, keep the following in
910 ``devtool build`` command on the recipe and then look in
923 within the recipe. Here is an example using :term:`EXTRA_OEMAKE`::
952 - Specify the name of the recipe such that it ends with "-native".
953 Specifying the name like this produces a recipe that only builds for
957 command. Specifying this option creates a recipe file that still
968 recipe file.
983 generated and pointed to by the recipe in order to freeze the version
996 - In order to support adding Node.js modules, a ``nodejs`` recipe
1013 When building a recipe using the ``devtool build`` command, the typical
1036 If you look at the contents of a recipe, you will see that the recipe
1039 the ``inherit`` directive. This technique leaves the recipe to describe
1060 recipe. The following locations under ``oe-workdir`` are particularly
1065 Within a recipe, this directory is referred to by the expression
1074 produced by the recipe. For more information, see the
1083 If the software your recipe is building uses GNU autoconf, then a fixed
1088 set within the recipe. If you wish to pass additional options, add them
1125 when a recipe is modified or removed. Thus, the sysroot is able to
1141 the recipe, and into several other packages. This separation exists
1144 a production image. Consequently, for each recipe the documentation
1149 After building a recipe, you can see where files have gone by looking in
1158 (i.e. the main package has the same name as the recipe and
1160 recipe name). The order of the :term:`PACKAGES` value is significant. For
1164 you do not even need to set these variables in your recipe unless the
1165 software the recipe is building installs files into non-standard
1171 If you use the ``devtool deploy-target`` command to write a recipe's
1178 any other files the recipe deployed. Consider the following example::
1214 need to link to libGL but you are not sure which recipe provides libGL.
1219 A free implementation of the OpenGL API Once you know the recipe
1233 if there is no recipe for the item you want to add to the SDK, you must