Lines Matching full:you
21 In addition to the functionality available through ``devtool``, you can
31 tailored to the contents of a specific image. You would use the
32 Extensible SDK if you want a toolchain experience supplemented with the
44 The first thing you need to do is install the SDK on your :term:`Build
47 You can download a tarball installer, which includes the pre-built
90 As an alternative to downloading an SDK, you can build the SDK
96 into the ``poky_sdk`` folder in your home directory. You can choose to
97 install the extensible SDK in any location when you run the installer.
99 the normal course of operation, the location you choose for installation
109 If you do not have write permissions for the directory into which you
110 are installing the SDK, the installer notifies you and exits. For
120 You are about to install the SDK to "/home/scottrif/poky_sdk". Proceed [Y/n]? Y
132 …Each time you wish to use the SDK in a new shell session, you need to source the environment setup…
138 Once you have the SDK installed, you must run the SDK environment setup
139 script before you can actually use the SDK. This setup script resides in
140 the directory you chose when you installed the SDK, which is either the
141 default ``poky_sdk`` directory or the directory you chose during
145 architecture for which you are developing. Environment setup scripts
154 SDK environment now set up; additionally you may now run devtool to perform development tasks.
160 :term:`LD`, and so forth). If you want to
168 ``devtool``. This tool provides a number of features that help you
177 is not limited to the extensible SDK. You can use
179 to help you easily develop any project whose build output must be
184 sub-commands for each function. You can run ``devtool --help`` to see
201 - *devtool modify*: Sets up an environment to enable you to modify
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
211 patch it. In both cases, an environment is set up so that when you build
213 allow you to make changes to the source as desired. By default, new
226 to allow you to extract source code into both the workspace or a
230 Depending on your particular scenario, the arguments and options you use
232 shows common development flows you would use with the ``devtool add``
239 scenarios by which you could use ``devtool add`` to generate a recipe
244 developer, you are probably interested in using that source code as
245 part of your development within the Yocto Project. All you need is
255 to the default workspace - you do not want the files in some
256 specific location outside of the workspace. Thus, everything you
264 corresponding append file in the workspace. If you do not provide
280 extracted code outside of the workspace. You need to specify an
311 2. *Edit the Recipe*: You can use ``devtool edit-recipe`` to open up the
317 From within the editor, you
318 can make modifications to the recipe that take effect when you build
321 3. *Build the Recipe or Rebuild the Image*: The next step you take
322 depends on what you are going to do with the new code.
324 If you need to eventually move the build output to the target
330 On the other hand, if you want an image to contain the recipe's
332 (e.g. for testing purposes), you can use the ``devtool build-image``
337 4. *Deploy the Build Output*: When you use the ``devtool build`` command
338 to build out your recipe, you probably want to see if the resulting
343 This step assumes you have a previously built image that is
347 on real hardware, you have network access to and from your
350 You can deploy your build output to that target hardware by using the
354 You can, of course, also deploy the image you build to actual
356 ``devtool`` does not provide a specific command that allows you to
370 Any changes you want to turn into patches must be committed to the
377 the standard layers and the upstream source is restored so that you
382 You can use the
384 command to put things back should you decide you do not want to
385 proceed with your work. If you do use this command, realize that
393 software. The command is flexible enough to allow you to extract code
398 Depending on your particular scenario, the arguments and options you use
407 scenarios by which you could use ``devtool modify`` to prepare to
448 Additionally, if you have any non-patch local files (i.e. files
452 Copying the files here gives you a convenient area from which you
453 can modify the files. Any changes or additions you make to those
454 files are incorporated into the build the next time you build the
455 software just as are other changes you might have made to the
473 You cannot provide a URL for
489 files are extracted to the location you provide with ``srctree``.
506 subdirectory does not exist and you run the ``devtool finish``
508 are removed because it appears to ``devtool`` that you have
515 2. *Edit the Source*: Once you have used the ``devtool modify`` command,
516 you are free to make changes to the source files. You can use any
517 editor you like to make and save your source code modifications.
519 3. *Build the Recipe or Rebuild the Image*: The next step you take
520 depends on what you are going to do with the new code.
522 If you need to eventually move the build output to the target
527 On the other hand, if you want an image to contain the recipe's
529 (e.g. for testing purposes), you can use the ``devtool build-image``
532 4. *Deploy the Build Output*: When you use the ``devtool build`` command
533 to build out your recipe, you probably want to see if the resulting
538 This step assumes you have a previously built image that is
542 on real hardware that you have network access to and from your
545 You can deploy your build output to that target hardware by using the
552 You can, of course, use other methods to deploy the image you built
569 Any changes you want to turn into patches must be staged and
570 committed within the local Git repository before you use the
577 by layer. Any work you did in the ``oe-local-files`` directory is
582 the standard layers and the upstream source is restored so that you
587 You can use the
589 command to put things back should you decide you do not want to
590 proceed with your work. If you do use this command, realize that
599 publishers. You can use the ``devtool upgrade`` workflow to make sure
600 your recipes you are using for builds are up-to-date with their upstream
605 Several methods exist by which you can upgrade recipes -
607 happens to be one. You can read about all the methods by which you
612 The ``devtool upgrade`` command is flexible enough to allow you to
626 scenario by which you use the ``devtool upgrade`` command. 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
647 If you want the code extracted to any other location, you need to
654 In this example, the "-V" option specifies the new version. If you
659 recipe are in a Git repository, you must provide the "-S" option and
668 Additionally, if you have any non-patch local files (i.e. files
672 Copying the files here gives you a convenient area from which you can
673 modify the files. Any changes or additions you make to those files
674 are incorporated into the build the next time you build the software
675 just as are other changes you might have made to the source.
681 such cases, you need to resolve the conflicts by editing the source
688 3. *Build the Recipe or Rebuild the Image*: The next step you take
689 depends on what you are going to do with the new code.
691 If you need to eventually move the build output to the target
696 On the other hand, if you want an image to contain the recipe's
698 (e.g. for testing purposes), you can use the ``devtool build-image``
703 4. *Deploy the Build Output*: When you use the ``devtool build`` command
704 or ``bitbake`` to build your recipe, you probably want to see if the
709 This step assumes you have a previously built image that is
713 on real hardware that you have network access to and from your
716 You can deploy your build output to that target hardware by using the
720 You can, of course, also deploy the image you build using the
722 ``devtool`` does not provide a specific command that allows you to do
731 Any work you did in the ``oe-local-files`` directory is preserved in
735 If you specify a destination layer that is the same as the original
744 Any changes you want to turn into patches must be committed to the
748 the standard layers and the upstream source is restored so that you
753 You can use the
755 command to put things back should you decide you do not want to
756 proceed with your work. If you do use this command, realize that
763 source tree you provide with the command. Currently, the command has
791 In most cases, you need to edit the automatically generated recipe in
792 order to make it build properly. Typically, you would go through
794 Once the recipe builds, you could use possible further iterations to
803 If you do not specify a name and version on the command line,
810 an error. For such cases, you must re-run the command and provide the
815 incorrect. For such a case, you must reset the recipe::
819 After running the ``devtool reset`` command, you need to
832 is not available. For cases where the dependency is not available, you
834 satisfies the dependency. Once you add that recipe, you need to update
838 If you need to add runtime dependencies, you can do so by adding the
851 details. In some cases, you might find you can substitute the
858 The ``devtool add`` command attempts to determine if the software you
862 You should double-check the value added by the command against the
863 documentation or source files for the software you are building and, if
871 recognize those license statements. Consequently, you might need to
875 correct licensing should you upgrade the recipe to a newer upstream
876 version in future. Any change in licensing is detected and you receive
877 an error prompting you to check the license text again.
881 :term:`LIC_FILES_CHKSUM` value unset. This behavior allows you to continue
883 all cases. You should check the documentation or source files for the
884 software you are building to determine the actual license.
903 - You probably need to patch the Makefile to use variables instead of
912 a list of environment variables that are set. You can take
917 desirable. For this case, you can either patch the Makefile so it
918 sets the default using the "?=" operator, or you can alternatively
941 ``ldconfig``. For such cases, you might be able to apply patches that
947 Often, you need to build additional tools that run on the :term:`Build
949 the target. You should indicate this requirement by using one of the
950 following methods when you run ``devtool add``:
963 If you need to add a tool that is shipped as part of a source tree
964 that builds code for the target, you can typically accomplish this by
967 "--also-native" option, you can add the tool using just one
973 You can use the ``devtool add`` command two different ways to add
990 - You must use quotes around the URL. The ``devtool add`` does not
999 As mentioned earlier, you can also add Node.js modules directly from a
1036 If you look at the contents of a recipe, you will see that the recipe
1077 You can use these links to get more information on what is happening at
1088 set within the recipe. If you wish to pass additional options, add them
1093 for Scons, and so forth). If you need to pass anything on the ``make``
1094 command line, you can use :term:`EXTRA_OEMAKE` or the
1098 You can use the ``devtool configure-help`` command to help you set the
1100 exact options being passed, and shows them to you along with any custom
1102 :term:`PACKAGECONFIG_CONFARGS`. If applicable, the command also shows you
1132 However, if you examine how build output gets into the final image on
1143 example, you probably do not need any of the documentation installed in
1149 After building a recipe, you can see where files have gone by looking in
1163 :term:`FILES` variables have default values. Consequently, you might find
1164 you do not even need to set these variables in your recipe unless the
1171 If you use the ``devtool deploy-target`` command to write a recipe's
1172 build output to the target, and you are working on an existing component
1173 of the system, then you might find yourself in a situation where you
1176 command backs up any files it overwrites, you can use the
1182 If you have deployed
1183 multiple applications, you can remove them all using the "-a" option
1200 on the target device (e.g. RPM or OPKG). Consequently, you should not
1211 populated on-demand. Sometimes you must explicitly install extra items
1212 into the SDK. If you need these extra items, you can first search for
1213 the items using the ``devtool search`` command. For example, suppose you
1214 need to link to libGL but you are not sure which recipe provides libGL.
1215 You can use the following command to find out::
1219 A free implementation of the OpenGL API Once you know the recipe
1220 (i.e. ``mesa`` in this example), you can install it::
1227 source, you can add the "-s" option as follows::
1233 if there is no recipe for the item you want to add to the SDK, you must
1239 If you are working with an installed extensible SDK that gets
1240 occasionally updated (e.g. a third-party SDK), then you will need to
1248 default update URL for you through the :term:`SDK_UPDATE_URL`
1251 section. If the SDK provider has not set that default URL, you need to
1258 SDK installer that you would download and install.
1263 You might need to produce an SDK that contains your own custom
1264 libraries. A good example would be if you were a vendor with customers
1267 you can produce a derivative SDK based on the currently installed SDK
1270 1. If necessary, install an extensible SDK that you want to use as a
1275 3. Add the extra libraries or other components you want by using the