On Fri, 2012-03-23 at 23:30 +0100, Martin Jansa wrote: > Signed-off-by: Martin Jansa <[email protected]> > --- > meta/recipes-support/libusb/libusb-compat_0.1.3.bb | 7 +++++-- > meta/recipes-support/libusb/libusb1_1.0.8.bb | 2 ++ > 2 files changed, 7 insertions(+), 2 deletions(-)
Looking at this, it makes no sense. Why does our build system need to be trying to extract information from the *native* system's USB bus? I can understand pango and cairo for font rendering in something like icons but libusb-native? Are you really sure we need this and have no other options as I can't see it actually being used... Looking at the other patches, I'm guessing they're broken without your PACKAGECONFIG change to fix -natives. A goal of this release is to have everything building and working that we ship. These 'simple' BBCLASSEXTENDs are likely going to change that. I don't really want to spend my weekend trying to fix and then test the PACKAGECONFIG change so I can merge these patches, particular as I've spent most of the week including the evenings just getting things to build. Arguably there could be other PACKAGECONFIG issue already I guess so we probably should fix that before release anyway. With -rc1 on Monday, that will be tricky :(. Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
