If texinfo-native is added to ASSUME_PROVIDED, this will be needed for two reasons. First, a world build will still build the native texinfo recipe, so it will still get test coverage and will not rot. Second, when the target architecture texinfo recipe is built, the native recipe must be built first so its makedoc binary can be extracted, ASSUME_PROVIDED or no.
Signed-off-by: Max Eliaser <max.elia...@intel.com> --- meta/recipes-extended/texinfo/texinfo_5.2.bb | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/meta/recipes-extended/texinfo/texinfo_5.2.bb b/meta/recipes-extended/texinfo/texinfo_5.2.bb index c1ccaa7..be90aba 100644 --- a/meta/recipes-extended/texinfo/texinfo_5.2.bb +++ b/meta/recipes-extended/texinfo/texinfo_5.2.bb @@ -7,7 +7,9 @@ SECTION = "console/utils" LICENSE = "GPLv3+" LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504" -DEPENDS = "zlib ncurses texinfo-native" +PROVIDES_append_class-native = " texinfo-replacement-native" + +DEPENDS = "zlib ncurses texinfo-replacement-native" DEPENDS_class-native = "zlib-native ncurses-native" TARGET_PATCH = "file://use_host_makedoc.patch" -- 1.8.3.2 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
