I see your point, seems like I got confused, I just checked and the resulting EXTRA_OECONF is the same, but I understand why this is conceptually wrong, I'll send a v2 in a bit.On 26 September 2017 at 18:23, Alejandro Hernandez <alejandro.hernandez@linux.intel.com> wrote:
Using EXTRA_OECONF_append gets added to the correct EXTRA_OECONF_class-<target/natve> correctly, otherwise its disregarded.
I guess the subtext was+EXTRA_OECONF_class-native = "\
+ --enable-ipv6=${@bb.utils.contains('DISTRO_FEATURES_ NATIVE', 'ipv6', 'yes', 'no', d)} \
That is totally wrong. In a native recipe, DISTRO_FEATURES has been altered based on DISTRO_FEATURES_NATIVE. You don't need to make other changes, and I suspect that reverting this chunk means the other chunks can also be reverted.
Ross