Skip to contentSkip to conversation

doc: Clarify how task dependencies relate to RDEPENDS

PATCH In review Jacob Kroon 3 participants 3 messages May 26, 2020 – May 28, 2020

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 doc: Clarify how task dependencies relate to RDEPENDS

Clarify that BitBake knows how to map entries defined in the runtime dependency namespace back to build-time dependencies (recipes) in which tasks are defined.

---
 doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 3 +++
 1 file changed, 3 insertions(+)
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +3 -0
index 10b58835..95a8b95b 100644
@@ -2526,6 +2526,9 @@
                 In the previous example, the <filename>do_packagedata</filename>
                 task of each item in <filename>RDEPENDS</filename> must have
                 completed before <filename>do_package_qa</filename> can execute.
+                Although <filename>RDEPENDS</filename> contains entries from the
+                runtime dependency namespace, BitBake knows how to map them back
+                to the build-time dependency namespace, in which the tasks are defined.
             </para>
         </section>
 
#1 lore raw
Quoted 14 lines · Jacob Kroon

Clarify that BitBake knows how to map entries defined in the runtime dependency namespace back to build-time dependencies (recipes) in which tasks are defined.

---
 doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 3 +++
 1 file changed, 3 insertions(+)
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +0 -0
index 10b58835..95a8b95b 100644

doc/bitbake-user-manual/bitbake-user-manual-metadata.xml line 2531

Quoted 6 lines
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +3 -0
@@ -2526,6 +2526,9 @@
                 In the previous example, the <filename>do_packagedata</filename>
                 task of each item in <filename>RDEPENDS</filename> must have
                 completed before <filename>do_package_qa</filename> can execute.
+                Although <filename>RDEPENDS</filename> contains entries from the
+                runtime dependency namespace, BitBake knows how to map them back
+                to the build-time dependency namespace, in which the tasks are defined.

That is quite an important clarification!

While working on multiconfig, I faced this issue - I can get build dependencies covered by "mcdepends", but there's no way to pull the resulting packages into images or SDK, as RDEPENDS or anything that results in RDEPENDS (IMAGE_INSTALL, PACKAGE_INSTALL, etc) all trigger this build-time dependency namespace check in bitbake and end up in errors like "Nothing RPROVIDES <blah>".
I wonder if multiconfig-aware RDEPENDS is needed to bypass this?

Signature · 1 line
Denys
#2 lore raw
Quoted 24 lines · Denys Dmytriyenko
Quoted 14 lines · Jacob Kroon

Clarify that BitBake knows how to map entries defined in the runtime dependency namespace back to build-time dependencies (recipes) in which tasks are defined.

---
 doc/bitbake-user-manual/bitbake-user-manual-metadata.xml | 3 +++
 1 file changed, 3 insertions(+)
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +0 -0
index 10b58835..95a8b95b 100644

doc/bitbake-user-manual/bitbake-user-manual-metadata.xml line 2531

Quoted 6 lines
doc/bitbake-user-manual/bitbake-user-manual-metadata.xml +3 -0
@@ -2526,6 +2526,9 @@
                 In the previous example, the <filename>do_packagedata</filename>
                 task of each item in <filename>RDEPENDS</filename> must have
                 completed before <filename>do_package_qa</filename> can execute.
+                Although <filename>RDEPENDS</filename> contains entries from the
+                runtime dependency namespace, BitBake knows how to map them back
+                to the build-time dependency namespace, in which the tasks are defined.

That is quite an important clarification!

Quoted 7 lines

While working on multiconfig, I faced this issue - I can get build dependencies covered by "mcdepends", but there's no way to pull the resulting packages into images or SDK, as RDEPENDS or anything that results in RDEPENDS (IMAGE_INSTALL, PACKAGE_INSTALL, etc) all trigger this build-time dependency namespace check in bitbake and end up in errors like "Nothing RPROVIDES <blah>".
I wonder if multiconfig-aware RDEPENDS is needed to bypass this?

Possibly. The challenge is that this RDEPENDS resolution is already horribly complicated and I'm not sure such dependencies are going to be at all easy to implement :(.

Cheers,

Richard