Lines Matching refs:recipe
42 Beginning work on a recipe:
43 add Add a new recipe
44 modify Modify the source for an existing recipe
45 upgrade Upgrade an existing recipe
48 latest-version Report the latest version of an existing recipe
51 Working on a recipe in the workspace:
52 build Build a recipe
53 rename Rename a recipe file in the workspace
54 edit-recipe Edit a recipe file
55 find-recipe Find a recipe file
57 update-recipe Apply changes from external source tree to recipe
58 reset Remove a recipe from your workspace
59 finish Finish working on a recipe in your workspace
61 deploy-target Deploy recipe output files to live target machine
62 undeploy-target Undeploy recipe output files in live target machine
63 build-image Build image including workspace recipe packages
66 extract Extract the source for an existing recipe
67 sync Synchronize the source tree for an existing recipe
68 menuconfig Alter build-time configuration for a recipe
89 …Adds a new recipe to the workspace to build a specified source tree. Can optionally fetch a remote…
92 …recipename Name for new recipe to add (just name - no version, path or extension). If n…
103 Version to use within recipe (PV)
107 …--autorev, -a When fetching from a git repository, set SRCREV in the recipe to a floating …
111 …--also-native Also add native variant (i.e. support building recipe for the build host as …
115 Specify an alias for the item provided by the recipe. E.g. virtual/libgl
136 run "devtool add", make changes to the recipe, and then
139 want the recipe.
153 added recipe. devtool places the recipe.bb file
157 when building the recipe. This is the default directory used
160 set of source files matched to a corresponding recipe.
162 .. _devtool-adding-a-new-recipe-to-the-workspace:
167 Use the ``devtool add`` command to add a new recipe to the workspace
168 layer. The recipe you add should not exist - ``devtool`` creates it for
169 you. The source files the recipe uses should exist in an external area.
171 The following example creates and adds a new recipe named ``jackson`` to
177 If you add a recipe and the workspace layer does not exist, the command
182 to add the recipe, append files, and source files into the existing
188 If your recipe has runtime dependencies defined, you must be sure
220 If you prefer to use the latest revision every time the recipe is
223 .. _devtool-extracting-the-source-for-an-existing-recipe:
229 existing recipe. When you use this command, you must supply the root
230 name of the recipe (i.e. no version, paths, or extensions), and you must
243 source tree for an existing recipe. When you use this command, you must
244 supply the root name of the recipe (i.e. no version, paths, or
252 .. _devtool-modifying-a-recipe:
258 existing recipe. This command is very similar to the
259 :ref:`add <devtool-adding-a-new-recipe-to-the-workspace>` command
260 except that it does not physically create the recipe in the workspace
261 layer because the recipe already exists in an another layer.
263 The ``devtool modify`` command extracts the source for a recipe, sets it
266 the recipe as commits on top. You can use the following command to
269 $ devtool modify recipe
271 Using the above command form, ``devtool`` uses the existing recipe's
276 .. _devtool-edit-an-existing-recipe:
281 Use the ``devtool edit-recipe`` command to run the default editor, which
282 is identified using the ``EDITOR`` variable, on the specified recipe.
284 When you use the ``devtool edit-recipe`` command, you must supply the
285 root name of the recipe (i.e. no version, paths, or extensions). Also,
286 the recipe file itself must reside in the workspace as a result of the
289 .. _devtool-updating-a-recipe:
294 Use the ``devtool update-recipe`` command to update your recipe with
297 :ref:`devtool modify <devtool-modifying-a-recipe>` command to extract
303 ``devtool update-recipe`` to create the patches and update the recipe::
305 $ devtool update-recipe recipe
307 If you run the ``devtool update-recipe``
311 your own layer rather than apply them to the original recipe. If so, you
313 ``devtool update-recipe`` command. These options allow you to specify
316 $ devtool update-recipe recipe -a base-layer-directory
323 .. _devtool-checking-on-the-upgrade-status-of-a-recipe:
329 need to determine if you can upgrade a recipe to a newer version.
331 To check on the upgrade status of a recipe, you can use the
332 ``devtool latest-version recipe`` command, which quickly shows the current
337 a new upstream version is available. Each such recipe will have its current
353 - For the ``oe-core`` layer, recipe maintainers come from the
357 …- If the recipe is using the :ref:`bitbake:bitbake-user-manual/bitbake-user-manual-fetching:git f…
359 the recipe's latest version tag, or in the absence of suitable tags,
361 in the recipe).
368 usage: devtool check-upgrade-status [-h] [--all] [recipe [recipe ...]]
373 recipe Name of the recipe to report (omit to report upgrade info for all recipes)
379 Unless you provide a specific recipe name on the command line, the
383 Notice the reported reason for not upgrading the ``base-passwd`` recipe.
387 the :term:`RECIPE_NO_UPDATE_REASON` variable to the corresponding recipe.
403 in a recipe when there's currently no way to determine its latest upstream
406 .. _devtool-upgrading-a-recipe:
418 Before you upgrade a recipe, you can check on its upgrade status. See
419 the ":ref:`devtool-checking-on-the-upgrade-status-of-a-recipe`" section
422 The ``devtool upgrade`` command upgrades an existing recipe to a more
423 recent version of the recipe upstream. The command puts the upgraded
424 recipe file along with any associated files into a "workspace" and, if
426 upgrade, patches associated with the recipe are rebased or added as
430 name of the recipe (i.e. no version, paths, or extensions), and you must
439 ":ref:`sdk-manual/extensible:use \`\`devtool upgrade\`\` to create a version of the recipe that sup…
445 .. _devtool-resetting-a-recipe:
450 Use the ``devtool reset`` command to remove a recipe and its
452 workspace layer. Realize that this command deletes the recipe and the
455 recipe and the append file outside of the workspace layer before running
458 If the ``devtool reset`` command detects that the recipe or the append
463 ``mtr`` recipe::
466 NOTE: Cleaning sysroot for recipe mtr...
470 .. _devtool-building-your-recipe:
475 Use the ``devtool build`` command to build your recipe. The
480 name of the recipe (i.e. do not provide versions, paths, or extensions).
484 $ devtool build recipe
495 to edit your custom image recipe appropriately.
507 Use the ``devtool deploy-target`` command to deploy the recipe's build
510 $ devtool deploy-target recipe target
531 - You are deploying a new application to the target and the recipe you
562 $ devtool undeploy-target recipe target
603 :ref:`devtool add <ref-manual/devtool-reference:adding a new recipe to the workspace layer>`
604 to create and add the ``mtr_0.86.bb`` recipe to the ``workspace`` directory::
616 recipes. The command matches the recipe name, package name, description,
617 and installed files. The command displays the recipe name as a result of