From: Denys Dmytriyenko <denys@ti.com>
To: "Maupin, Chase" <chase.maupin@ti.com>
Cc: meta-ti mailing list <meta-ti@yoctoproject.org>
Subject: Re: curious about libdrm-2.4.41 recipe from meta-ti layer
Date: Fri, 18 Jul 2014 11:44:08 -0400 [thread overview]
Message-ID: <20140718154408.GG15788@edge> (raw)
In-Reply-To: <7D46E86EC0A8354091174257B2FED1015D15411B@DLEE11.ent.ti.com>
On Fri, Jul 18, 2014 at 03:30:57PM +0000, Maupin, Chase wrote:
> >-----Original Message-----
> >From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> >bounces@yoctoproject.org] On Behalf Of Robert P. J. Day
> >Sent: Friday, July 18, 2014 6:47 AM
> >To: meta-ti mailing list
> >Subject: [meta-ti] curious about libdrm-2.4.41 recipe from meta-ti
> >layer
> >
> >
> > i was perusing a number of yocto layers looking for cool
> >examples to
> >use in an upcoming class and ran across this oddity in the meta-ti
> >layer:
> >
> >recipes-graphics/drm/libdrm_2.4.41.bb:
> > FILESEXTRAPATHS_append := ":${COREBASE}/meta/recipes-
> >graphics/drm/libdrm"
> >
> > in all of the layers i've looked at, that is the only example of
> >*appending* to FILESEXTRAPATHS i've ever seen, so i thought i'd
> >look
> >closer to see what was going on.
> >
> > even though oe-core defines a libdrm recipe file, the meta-ti
> >layer
> >doesn't use a bbappend for its version. rather, it explicitly adds
> >the
> >libdrm/ directory from oe-core using a reference to ${COREBASE},
> >then
> >adds its own files. that's valid, i guess, it just looks weird and
> >is
> >the only time i've ever seen that.
>
> The recipe also defines using a TI version of libdrm (I don't like that but
> it is what we have been given from the component team doing this). So the
> intent here is to:
>
> 1. Define a libdrm that uses the TI modified sources.
> 2. Use the recipe only for the omap-a15 devices and make that an explicit
> setting by setting default preference to -1.
>
> This wasn't done as an append because we wanted this only for omap-a15
> devices when explicitely set as the preferred version to use and not impact
> other devices using the later version from oe-core.
>
> As for the reference to COREBASE it is to pick up the
> GNU_SOURCE_definition.patch file rather than overlaying that as well.
Heh, if I knew you were already replying to this, I would have avoided
duplicating the effort...
> > i'm also puzzled that the meta-ti recipe sets:
> >
> >DEFAULT_PREFERENCE = "-1"
> >
> >what's that for? given that the oe-core layer already defines a
> >recipe for libdrm that has a higher version number, why would the
> >above line be necessary?
> >
> > just trying to understand the rationale behind this unusual
> >construction.
> >
> >rday
> >
> >--
> >
> >==================================================================
> >======
> >Robert P. J. Day Ottawa, Ontario,
> >CANADA
> > http://crashcourse.ca
> >
> >Twitter:
> >http://twitter.com/rpjday
> >LinkedIn:
> >http://ca.linkedin.com/in/rpjday
> >==================================================================
> >======
> >
> >--
> >_______________________________________________
> >meta-ti mailing list
> >meta-ti@yoctoproject.org
> >https://lists.yoctoproject.org/listinfo/meta-ti
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2014-07-18 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 11:46 curious about libdrm-2.4.41 recipe from meta-ti layer Robert P. J. Day
2014-07-18 15:30 ` Maupin, Chase
2014-07-18 15:44 ` Denys Dmytriyenko [this message]
2014-07-18 15:37 ` Denys Dmytriyenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140718154408.GG15788@edge \
--to=denys@ti.com \
--cc=chase.maupin@ti.com \
--cc=meta-ti@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.