Hello David, There is nothing really special compared to "usual" recipes or whatever you use RPM or another packager.
In short: 1) You should create (likely in a layer of yours) the recipe for your "third-party" package. You should put in this package the right dependencies (using either DEPENDS or RDEPENDS, depending if it is build or runtime dependency) and of course any other parts needed to build/install it. 2) Of course should your new package depend on packages that are not already in Yocto, you should create as well recipes for those. If they are already in Yocto, you will just refer to them. 3) You should do (in your layer) an image recipe or extend the core-image-base, adding your new recipe. You don't really need to add all the dependencies there but just your final package, the dependencies will be automatically (depending on the definitions in recipes) be pulled in. 4) the fact that is a RPM (or deb, or ipk) is just a detail, things will work in image generation the same way. What will change is then of course possibly how you manage those packages at runtime (ie. updates or the like). I guess most of the things shortly mentioned above are then well documented here: https://wiki.yoctoproject.org/wiki/Building_your_own_recipes_from_first_principles Hope that helps, Federico Il giorno gio 8 dic 2022 alle ore 17:56 <[email protected]> ha scritto: > Hello, > I need to deploy a third-party package as part of my Yocto image. I am > not sure how to build a recipe that will automate the installation of this > RPM and dependencies. If any of these dependent packages are not already > included in the core-image-base image, I'll have to put together recipes > for those as well and add them to the main recipe for the package (the RPM > I want to install). I have a basic idea of what needs to be done but am > fuzzy on the detail. I'll need to create a recipe that points to my RPM > file via SRC_URI, but I am not sure what commands need to be included to > make sure the RPM is seen as a package I can add via my local.conf. The > goal is to have the package installed in the final image such that the > software is running as if the RPM was installed manually at the command > prompt on the target board. I've done a lot of googling, but the few > posts I could find contain bits of information that aren't that useful to a > Yocto newbie. Note that I am using latest version of Kirkstone. > > Thanks! > > David > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58769): https://lists.yoctoproject.org/g/yocto/message/58769 Mute This Topic: https://lists.yoctoproject.org/mt/95542036/21656 Mute #bitbake:https://lists.yoctoproject.org/g/yocto/mutehashtag/bitbake Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
