From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1S863G-0005ac-AZ for openembedded-core@lists.openembedded.org; Thu, 15 Mar 2012 09:28:50 +0100 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q2F8K5w0018273 for ; Thu, 15 Mar 2012 08:20:05 GMT Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14799-10 for ; Thu, 15 Mar 2012 08:20:01 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q2F8JuB1018254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 15 Mar 2012 08:19:57 GMT Message-ID: <1331799594.18586.61.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Thu, 15 Mar 2012 08:19:54 +0000 In-Reply-To: References: X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Subject: Re: Task after do_package repeating despite stamp X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 08:28:50 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2012-03-15 at 01:11 +0000, Daniel Lazzari wrote: > 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? It looks like you're creating something machine specific since you're placing it in ${MACHINE}. This effectively makes anything depending on this task machine specific also. Cheers, Richard