style question about assigning to FILES_${PN}

style question about assigning to FILES_${PN}

[Robert P. J. Day]

  i've seen a number of recipes bounce around between these variations
of adding an entire directory to a package's files:

  FILES_${PN} = "dir"
  FILES_${PN} = "dir/"
  FILES_${PN} = "dir/*"

first, i'm assuming all of the above mean exactly the same thing, yes?
that the entire directory, recursively, is being added. i ask since
even the stock OE bitbake.conf seems to jump around in the space of a
few lines:

  FILES_${PN} = "${bindir}/* ${sbindir}/* ${libexecdir}/* ${libdir}/lib*${SOLIBS} \
            ${sysconfdir} ${sharedstatedir} ${localstatedir} \
            ${base_bindir}/* ${base_sbindir}/* \
            ... etc etc ...

hang on, what about hidden objects in the immediate subdirectory?
based on normal wildcarding, would the first two variants include
hidden files, while the third would not?

rday

Re: [OE-core] style question about assigning to FILES_${PN}

[Richard Purdie]

On Tue, 2021-04-06 at 12:28 -0400, Robert P. J. Day wrote:
>   i've seen a number of recipes bounce around between these variations
> of adding an entire directory to a package's files:
> 
>   FILES_${PN} = "dir"
>   FILES_${PN} = "dir/"
>   FILES_${PN} = "dir/*"
> 
> first, i'm assuming all of the above mean exactly the same thing, yes?

I don't think they do mean the same thing, no. I think some patch
all files in a directory and some match recursively.

Cheers,

Richard