On 22 September 2015 at 09:10, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> The longer stack trace is actually really helpful. I believe the code
> here should inherit the working directory of the current task rather
> than rely on the default of ${B} which bitbake assigns if there is
> nothing else.
>
> The trouble is that if the function does specify a dirs flag, it should
> really use that instead of a supplied parameter and if we use the
> parameter to exec_func(), it won't do that.
>
> There aren't that many uses of SSTATEPOSTINSTFUNCS in our metadata so
> the easiest way to fix this short term is probably to go through them
> and add specific [dirs] options to the functions.
>
There's enough instances of SSTATEPOSTINSTFUNCS dotted around even just
oe-core, but they're all going to be using SSTATE_INSTDIR as the working
directory. Whilst you have a valid point that the functions should respect
[dirs] if set, for the case of sstate post-install hooks I think we should
just force the right path so the recipe creators don't have to worry about
this.
Ross
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
