the do_deploy task has been added in kernel.bbclass, which defines the
proper order for these tasks. So it should be safe to remove 'addtask
deploy' from the recipe.
在 Sat, 23 Jan 2010 18:10:47 +0800，Martin Jansa <[email protected]>
写道:
On Sat, Jan 23, 2010 at 05:55:54PM +0800, Guo Hongruan wrote:
Yes, I did.
the same question exists in
recipes/linux/gumstix-linux.inc|72| addtask deploy before do_package
after do_install
which may cause circular dependency too.
But if you just remove that line, the custom do_deploy task won't be
used at all IIRC.. so proper fix would be to adjust after and before
like in a55e9a527a8c9823044196d031f2da2783ff8f35 and then
bc2bddb71d8c5db25b80aa6435392ec1c8df39f9
Probably:
addtask deploy before do_build after do_package
but please check
before do_build was needed to force it run at all (for -c build)
after do_package was used, because we're packing already stripped
modules to modules.tgz and we needed to have packages-split already
populated.
Regards,
--
Guo Hongruan, Embedded Linux Consultant
Skype: camelguo
Twitter: camelguo
http://www.gulessoft.com
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
