Re: do_configure() failure with my qt4-embedded_4.8.0.bbappend

[Paul Eggleton <paul.eggleton@linux.intel.com>]

On Tuesday 17 July 2012 15:49:16 Jon Szymaniak wrote:
> > From what I gather looking
> > at recipes-qt/qt4/* a bit, the point here is to rename libs to
> > differentiate between the libs generated by the embedded and X11-based
> > recipes, right?

That's correct.

> > I ended up including -qtlibinfix ${QT_LIBINFIX} in my config flags, and I
> > do indeed see that my  qt4-embbeded libs are now in the form libQt*E.so.
> > 
> > However, my builds are failing because ld complains about not being able
> > to
> > find QtDeclarative, QtGui, and QtCore.
> > 
> > Looking at the Makefile generated by qmake for one of my little HelloWorld
> > applications, I see that it seems that qmake did not accounted for the
> > 
> > "E" suffix:
> >   LIBS  = $(SUBLIBS)  -L$(OE_QMAKE_LIBDIR_QT) -lQtDeclarative -lQtGui
> > 
> > -lQtCore -lpthread
> > 
> > Just as a little experiment, I modified the generated Makefile to add
> > the "E" suffix,
> > to each lib and reran bitbake. This succeeded and my Qt app was built.
> > 
> > While I'm sure I could hack in a do_compile_prepend() to address this,
> > I'm assuming
> > that it's a configuration mess-up on my end. Given that I only changed
> > the DEPENDS
> > and QT_CONFIG_FLAGS in my .bbappend, I can't think of what I might have
> > neglected here that might be  affecting qmake or the mkspec.
> 
> Just to create a trail of breadcrumbs, the issue was that I was inheriting
> qmake2 in my app's recipe. I should have been inheriting qt4e. I see
> that this sets up QT_LIBINFIX as well as a number of other items.
> 
> See meta/classes/qt4e.bbclass.

Right, that's what I would have asked about - good detective work :)

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre