<br><br>On Wednesday, May 29, 2013, Mark Hatle <<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.com</a>> wrote:<br>> On 5/29/13 10:59 AM, Martin Jansa wrote:<br>>><br>>> On Wed, May 29, 2013 at 10:09:44AM -0500, Mark Hatle wrote:<br>
>>><br>>>> Add S(ource) and B(uild) directory information to the recipe pkgdata files.<br>>>> This allows external tools to find the appropriate information, and be able<br>>>> to easily access the corresponding sources and build directories.<br>
>>><br>>>> Signed-off-by: Mark Hatle <<a href="mailto:mark.hatle@windriver.com">mark.hatle@windriver.com</a>><br><br>Hi Mark<br><br>This won't work well when package is populated from sstate is there a way for it to work seamlessly across sstate it might be useful<br>
<br><br>>>> ---<br>>>> meta/classes/package.bbclass | 2 ++<br>>>> 1 file changed, 2 insertions(+)<br>>>><br>>>> diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass<br>
>>> index 02a1460..19b2b4c 100644<br>>>> --- a/meta/classes/package.bbclass<br>>>> +++ b/meta/classes/package.bbclass<br>>>> @@ -1124,6 +1124,8 @@ python emit_pkgdata() {<br>>>><br>
>>> data_file = pkgdatadir + d.expand("/${PN}" )<br>>>> f = open(data_file, 'w')<br>>>> + f.write("S: %s\n" % d.expand("${S}"))<br>>>> + f.write("B: %s\n" % d.expand("${B}"))<br>
>>> f.write("PACKAGES: %s\n" % packages)<br>>>> f.close()<br>>><br>>> how does this interact with sstate? does setscene task create<br>>> pkgdata with right paths?<br>
>><br>><br>> The pkgdata is always current to the current build/work directory. When the sstate-cache runs, and the associated pkgdata is dumped to the disk the S and B for the current directory is written. But when sstate-cache is used, there is no extracted source (or build) components so those directories remain unresolved.<br>
><br>> It's up to the tooling that are using these files to check if the directory exists, if it does not -- then using bitbake -c patch <recipe> will create it. (even in the sstate-cache case.)<br>><br>
> --Mark<br>> _______________________________________________<br>> Openembedded-core mailing list<br>> <a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
> <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>>