From: "Sreejith Ravi" <sreejith.ravi087@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] package.bbclass: Fix broken dev package dependency.
Date: Mon, 24 Jun 2024 06:02:02 -0700 [thread overview]
Message-ID: <2056.1719234122993514513@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj8LT7JyO1731na1c0a8+_rfoCSjwyr=QfMC4124QAT2kw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
We should be able to install the dev IPK and resolve its corresponding dependency chain. As I mentioned earlier, enabling recommended packages and installing them increases hard disk usage and installation time when installing a lot of unnecessary recommended packages.
Yocto handles the dev dependency chain by parsing the 'Requires' field from the .pc file in the package_do_pkgconfig function. However, there is one more field, 'Requires.private', which also needs to be considered when creating the dependency chain for the dev IPKs. With this, the dev IPK has the proper dependencies listed and there is no need to install the recommended packages.
[-- Attachment #2: Type: text/html, Size: 666 bytes --]
next prev parent reply other threads:[~2024-06-24 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 9:56 [PATCH] package.bbclass: Fix broken dev package dependency Sreejith Ravi
2024-06-24 11:07 ` [OE-core] " Alexander Kanavin
2024-06-24 11:20 ` Sreejith Ravi
2024-06-24 11:27 ` Alexander Kanavin
2024-06-24 12:23 ` Sreejith Ravi
2024-06-24 12:36 ` [OE-core] " Alexander Kanavin
2024-06-24 12:47 ` Sreejith Ravi
2024-06-24 12:53 ` [OE-core] " Alexander Kanavin
2024-06-24 13:02 ` Sreejith Ravi [this message]
2024-06-24 13:26 ` Alexander Kanavin
2024-06-24 13:34 ` Sreejith Ravi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2056.1719234122993514513@lists.openembedded.org \
--to=sreejith.ravi087@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox