Re: [morty][PATCH v2] Make ti-xdctools a native recipe

[Joshua Watt <jpewhacker@gmail.com>]

On Mon, 2017-12-18 at 13:08 -0500, Denys Dmytriyenko wrote:
> On Fri, Dec 15, 2017 at 06:09:28PM -0600, Joshua Watt wrote:
> > On Fri, 2017-12-15 at 17:59 -0500, Denys Dmytriyenko wrote:
> > > Thanks, have you tried building anything with this change?
> > > 
> > > Right off the bat it breaks ipumm-fw, as it expects xdctools to
> > > reside in the 
> > > same sysroot as BIOS, which is the target one. Fixing it.
> > 
> > Hmm... thats odd. I'm though we were building the ipumm-fw
> > recipe...
> > maybe not though. We are a ways behind on the morty branch right
> > now
> > (which is where our patch was based originally). I'll make sure to
> > get
> > us up to the HEAD and try it on Monday.
> > 
> > > Also, I'm making corresponding changes in meta-arago, which uses
> > > xdctools as 
> > > well. Hopefully there's not much breakage there...
> > 
> > We don't use much of meta-arago (our distro is poky based), but we
> > do
> > "cherry-pick" most of the non-qt based recipes through a rather
> > ugly
> > process from meta-arago-extra (I don't know if they all build
> > though).
> 
> Latest patches for meta-ti and meta-arago were posted to resolve
> discussed 
> above issues.

Thanks, we'll give it a try

> 
> 
> > On a side note, optional Qt support in meta-arago would be
> > *greatly*
> > appreciated :)
> 
> Can you be more specific? Do you have an exact components from meta-
> arago 
> that you want to build w/o Qt?
> 
> On the other hand, we only officially support Wayland on our
> platforms, not 
> X11. Thus there are some specific graphics requirements involved - if
> you are 
> trying to build something graphical, it will pull in Qt
> dependencies...

We are running Wayland (although it is our own custom compositor), so
thats not really the issue. I don't think we have any expectations to
be able to *build* recipes that depends on Qt. The problem we run into
is that we can't include meta-arago at all because it depends on
classes and such from meta-qt, which we aren't including. This prevents
the recipes from even parsing. This isn't a problem unique to meta-
arago, but meta-arago is the first one that have had to work around in
such an annoying fashion.

I think the main offender is qmake5.bbclass, but there might be others.
I don't really know of a good way to make these recipes parse when Qt
isn't present... the best I can think of off the top of my head would
be something like:

 inherit ${@bb.utils.contains('DISTRO_FEATURES', 'qt5', 'qmake5', '')}

I guess the other option would be to move stuff to meta-ti from meta-
arago? I don't know what qualifies something to be in one or the other.

I'm more than willing to put some patches together if you have any
thoughts.

Thanks,
Joshua Watt