[OE-core] [PATCH 2/21] Add directory information to the pkgdata files
Paul Eggleton
paul.eggleton at linux.intel.com
Wed May 29 15:11:13 UTC 2013
On Wednesday 29 May 2013 10:09:44 Mark Hatle wrote:
> Add S(ource) and B(uild) directory information to the recipe pkgdata files.
> This allows external tools to find the appropriate information, and be able
> to easily access the corresponding sources and build directories.
>
> Signed-off-by: Mark Hatle <mark.hatle at windriver.com>
> ---
> meta/classes/package.bbclass | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
> index 02a1460..19b2b4c 100644
> --- a/meta/classes/package.bbclass
> +++ b/meta/classes/package.bbclass
> @@ -1124,6 +1124,8 @@ python emit_pkgdata() {
>
> data_file = pkgdatadir + d.expand("/${PN}" )
> f = open(data_file, 'w')
> + f.write("S: %s\n" % d.expand("${S}"))
> + f.write("B: %s\n" % d.expand("${B}"))
> f.write("PACKAGES: %s\n" % packages)
> f.close()
I'm not sure I'm totally comfortable with this idea. External tools shouldn't
necessarily expect to be able to poke into the source after packaging occurs -
rm_work (if enabled) will remove the work directory, and separately sstate may
restore the pkgdata and not the workdir. In both situations these values will
be invalid.
If tools need to be able to find out the values of S and B then I think they
ought to be querying them via bitbake.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
More information about the Openembedded-core
mailing list