Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: two variations for distro-specific FILESEXTRAPATHS prepending
Date: Wed, 16 Jul 2014 07:26:38 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407160719540.5398@localhost> (raw)


  just ran across this in the meta-yocto layer but it's a general OE
question -- the psplash_git.bbappend file contains the following
distro-conditional line:

  FILESEXTRAPATHS_prepend_poky := "${THISDIR}/files:"

and the accompanying files/ directory has, unsurprisingly, a
poky-specific splash image file, "psplash-poky-img.h".

  but based on how FILESEXTRAPATHS is processed by incorporating all
of the FILESOVERRIDES variations (one of which is the distro name),
would it not have been entirely equivalent to have used simply

    FILESEXTRAPATHS_prepend := "${THISDIR}/files:"

and placed that splash file in the accompanying directory files/poky/?
would these two approaches do the same thing? is there a preferred
way? that's the only example of that i've seen in all the layers i've
played with.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



             reply	other threads:[~2014-07-16 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 11:26 Robert P. J. Day [this message]
2014-07-16 16:36 ` two variations for distro-specific FILESEXTRAPATHS prepending Christopher Larson
2014-07-16 19:26   ` Robert P. J. Day

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=alpine.LFD.2.11.1407160719540.5398@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox