From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187]) by mail.openembedded.org (Postfix) with ESMTP id B7A476CD55 for ; Fri, 18 Oct 2013 09:41:52 +0000 (UTC) Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r9I9fYfg018665; Fri, 18 Oct 2013 10:41:34 +0100 X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id S4dw8MVsxUox; Fri, 18 Oct 2013 10:41:34 +0100 (BST) Received: from [192.168.3.10] (rpvlan0 [192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r9I9fRpp018656 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 18 Oct 2013 10:41:29 +0100 Message-ID: <1382089284.29912.528.camel@ted> From: Richard Purdie To: "Robert P. J. Day" Date: Fri, 18 Oct 2013 10:41:24 +0100 In-Reply-To: References: X-Mailer: Evolution 3.6.4-0ubuntu1 Mime-Version: 1.0 Cc: OE Core mailing list Subject: Re: diff between defining a "no-op" task and using [noexec]? X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Oct 2013 09:41:53 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2013-10-17 at 08:07 -0400, Robert P. J. Day wrote: > using a concrete example, there's this from oe core's > linux-dummy.bb: > > do_configure() { > : > } > > do_compile () { > : > } > > do_install() { > : > } > > what is the difference between the above and writing: > > do_configure[noexec] = "1" > do_compile[noexec] = "1" > do_install[noexec] = "1" > > *is* there a difference? if so, does it have to do with the > processing of other flags for that task? > > i can see that, technically, the first variation still defines a > task to be run, while the second specifies that the task *not* be run, > so i can appreciate that those two operations have different results. The difference is just that, with the first case bitbake will run the task, it will do nothing. In the second case, bitbake will not bother running it at all. Cheers, Richard