>Date: Thu, 15 Mar 2012 01:11:00 +0000 >From: Daniel Lazzari <[email protected]> >Subject: [OE-core] Task after do_package repeating despite stamp >To: "[email protected]" > <[email protected]> >Message-ID: > <[email protected] >eapfrog.com> >Content-Type: text/plain; charset="us-ascii" > >Let me preface this by saying I'm running an older oe-core (Angstrom) so this >may be fixed in the latest, but if so, I'm hoping someone can point me at the >patch to fix it. > >I have a few recipes in our layer that need to generate proprietary packages >from ${D} after the do_package task has copied the files for its own devices. >To do this, I have a task like: > >do_create_foo() { > #Generate foo package here > foo_pkger ${D} ${DEPLOY_DIR}/foo/${MACHINE} >} >addtask create_foo after do_package before do_build >do_create_foo[dirs] = "${DEPLOY_DIR}/foo/${MACHINE}" > >The problem is, when building any recipe that depends on this recipe, it >reruns do_create_foo. This is especially problematic because we use >rm_work, so often when it goes back to rerun do_create_foo, ${D} no longer >exists. I checked and a stamp exists for the task. > >Anyone have any insight? Is anyone else seeing something like this? >
Upon closer inspection, there isn't actually a stamp for this, just a sigdata file. I put a quick tracer in bb.build.make_stamp and it is reaching this point. At the very least I am not as stuck as I thought I was. Help is still very much appreciated though if anyone knows what's going on. _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
