Re: kernel manual: confusing coverage of FILESEXTRAPATHS_prepend

["Robert P. J. Day" <rpjday@crashcourse.ca>]

On Thu, 26 Feb 2015, Robert P. J. Day wrote:

  ... snip ...

>   sort of related to this, but in a *regular* recipe (not a bbappend),
> the default FILESPATH is set in base.bbclass:
>
> FILESPATH = "${@base_set_filespath(["${FILE_DIRNAME}/${BP}",
> "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}"
>
> so that, by default, a regular recipe will look for SRC_URI entries in
> *all* of:
>
> 1) ${BP}/
> 2) ${BPN}/
> 3) "files/"
>
> it's not clear which is the preferred standard (not sure there even
> *is* a preferred standard), but in cases where more than one of the
> above exists, all of the relevant directories will be searched, but
> it's not clear why some recipes insist on breaking up the files over
> more than one directory.
>
>   in the case of subversion, i can see the logic:
>
> subversion/
> subversion_1.6.15.bb
> subversion-1.8.11/
> subversion_1.8.11.bb
>
> so that the generic "subversion/" directory will apply to *all*
> subversion recipes, but there is also the version-specific
> "subversion-1.8.11/", so that's fine.
>
>   busybox, though:
>
> busybox/
> busybox_1.23.1.bb
> busybox_git.bb
> busybox.inc
> files/
>
> won't both directories busybox/ and files/ always be consulted for
> SRC_URI entries, regardless of the version of busybox? so what is the
> rationale for breaking those files over two directories?
>
>   and i'm curious ... is there any recipe that contains all *three*
> types of SRC_URI subdirectories?

  just to follow up on this, as a demo of how to add a directory of
SRC_URI files to a basic recipe, i want to show a variety of
possibilities, from simple to complex.

  in the simplest case, there will be a single directory, which will
be named one of BP, BPN, or "files", all of which are equally valid --
lots of examples of this.

  slightly more complex -- a multi-version recipe directory with each
recipe version having its own version-specific directory, like
coreutils:

coreutils-6.9/
coreutils_6.9.bb
coreutils-8.23/
coreutils_8.23.bb

  more complicated -- recipes with *both* version-specific and generic
directories like, say, readline:

files/
readline-5.2/
readline_5.2.bb
readline-6.3/
readline_6.3.bb
readline.inc

etc, etc. when this is explained in the appropriate YP manual, is it
clear the variety you can have?

rday

-- 

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

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