10197 2016-08-31 06:44:58 +0000 Suggested additions to the MLPREFIX glossary entry 2016-09-01 21:59:07 +0000 1 1 9 Documentation Reference handbook 2.2 x86 Multiple RESOLVED FIXED 01 Sept 2016: RESOLVED Medium normal 2.2 M4 1 ulfalizer srifenbark bluelightning poky.doc.watcher poky.watcher srifenbark --- --- Done (doc changes complete) oldest_to_newest 65628 0 ulfalizer 2016-08-31 06:44:58 +0000 Hello, I think adding the following to the end of the MLPREFIX glossary entry would demystify it a lot: Note { The "ML" in MLPREFIX stands for "MultiLib". This is historical and comes from a time when 'nativesdk' was a suffix rather than a prefix on the recipe name. When 'nativesdk' was turned into a prefix, it made sense to set MLPREFIX for it as well. } An example situation where MLPREFIX might be needed is when using [BBCLASSEXTEND] to provide a nativesdk version of a recipe in addition to the target version. If that recipe declares build-time dependencies on tasks in other recipes by using [DEPENDS], then a dependency on "foo" will automatically get rewritten to a dependency on "nativesdk-foo". However, dependencies like the following will not get rewritten automatically: do_foo[depends] += "some-recipe:do_foo" If you want such a dependency to also get transformed, you can do the following: do_foo[depends] += "${MLPREFIX}some-recipe:do_foo" Cheers, Ulf 65725 1 srifenbark 2016-09-01 21:17:38 +0000 Ulf, See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-MLPREFIX Thanks, Scott 65731 2 ulfalizer 2016-09-01 21:49:19 +0000 Looks fine to me. Thanks, Ulf 65739 3 srifenbark 2016-09-01 21:59:07 +0000 Thanks, Setting to RESOLVED and putting the doc flag to "done." Scott