Hi, is it true that that PACKAGECONFIG is only used for recipes that inherit autoconf?
Was trying to understand what they do in a recipe: https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-connectivity/bluez5/bluez5.inc and didn't really get what this was about until found the autoconf reference mentioned in a book. So "features" as referenced in the mega manual: https://www.yoctoproject.org/docs/2.4/mega-manual/mega-manual.html#var-PACKAGECONFIG are the flags that will end up being passed to ./configure? However later in the recipe it's used to populate other variables NOINST_TOOLS = " \ ${@bb.utils.contains('PACKAGECONFIG', 'readline', '${NOINST_TOOLS_READLINE}', '', d)} \ ${@bb.utils.contains('PACKAGECONFIG', 'testing', '${NOINST_TOOLS_TESTING}', '', d)} \ ${@bb.utils.contains('PACKAGECONFIG', 'tools', '${NOINST_TOOLS_BT}', '', d)} \ " Is the original assumption true (that it's an autoconf only thing)? Is there a way to test that by grepping the code (didn't found autoconf references when greping for PACKAGECONFIG in bitbake -e bluez5)? Be Well :) -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto