How to determine dependencies of recipes in yocto?

前端 未结 4 1670
时光说笑
时光说笑 2021-02-15 11:46

I want to add gedit to the the image. But i am not able to find the dependencies of gedit package. How to find the dependencies (DEPENDS) in yocto.

相关标签:
4条回答
  • 2021-02-15 12:28

    You can also use Toaster, which is a web UI that collects information about what you build, including dependencies. This video shows the dependency information provided:

    https://www.youtube.com/watch?v=x-6dx4huNnw

    Details on how to set up and use Toaster at

    www.yoctoproject.org/docs/latest/toaster-manual/toaster-manual.html

    0 讨论(0)
  • 2021-02-15 12:35

    You can use the following command which opens up a Dependency explorer that displays dependencies on the packages:

    bitbake -g recipe-name -u depexp

    or bitbake -g gedit -u depexp ,in your case.

    On pyro and later use:

    bitbake -g recipe-name -u taskexp

    Note: this command needs python-gtk2 installed.

    0 讨论(0)
  • 2021-02-15 12:39

    The list of packages installed in your image is stored in the manifest file (besides of build history which is already mentioned).

    Content of the manifest file looks like:

    alsa-conf cortexa7hf-neon-vfpv4 1.1.2-r0.1
    alsa-conf-base cortexa7hf-neon-vfpv4 1.1.2-r0.1
    alsa-lib cortexa7hf-neon-vfpv4 1.1.2-r0.1
    alsa-states cortexa7hf-neon-vfpv4 0.2.0-r5.1
    alsa-utils-alsactl cortexa7hf-neon-vfpv4 1.1.2-r0.5
    alsa-utils-alsamixer cortexa7hf-neon-vfpv4 1.1.2-r0.5
    ...
    

    The list consists of the package name, architecture and a version.

    That manifest is located in the deploy directory (i.e. deploy/images/${MACHINE}/). Here as an example of the directory listing (there are target images and the manifest file)

    example-image-genericx86.ext3
    example-image-genericx86.manifest
    example-image-genericx86.tar.bz2
    
    0 讨论(0)
  • 2021-02-15 12:47

    You find the dependencies by reading the build documentation and the build system scripts (in this case probably configure.ac) of the software in question, and then trial and error.

    You could also use Openembedded Metadata Index to find an existing recipe and use or update that: http://cgit.openembedded.org/cgit.cgi/meta-openembedded/tree/meta-gnome/recipes-gnome/gedit/gedit_2.30.4.bb

    0 讨论(0)
提交回复
热议问题