From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.cbnco.com ([207.164.182.72]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1PFyDi-0001iu-Dq for openembedded-devel@lists.openembedded.org; Wed, 10 Nov 2010 01:07:24 +0100 Received: from localhost (localhost [127.0.0.1]) by smtp.cbnco.com (Postfix) with ESMTP id 98ACB8EDACB for ; Tue, 9 Nov 2010 19:06:25 -0500 (EST) Received: from smtp.cbnco.com ([127.0.0.1]) by localhost (mail.cbnco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18780-07 for ; Tue, 9 Nov 2010 19:06:25 -0500 (EST) Received: from [172.20.22.83] (auriga-dmzgw.cbnco.com [207.164.182.65]) by smtp.cbnco.com (Postfix) with ESMTPSA id 79C778E1777 for ; Tue, 9 Nov 2010 19:06:25 -0500 (EST) Message-ID: <4CD9E201.3040808@cbnco.com> Date: Tue, 09 Nov 2010 19:06:25 -0500 From: Michael Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100228) MIME-Version: 1.0 To: openembedded-devel X-Virus-Scanned: amavisd-new at cbnco.com X-SA-Exim-Connect-IP: 207.164.182.72 X-SA-Exim-Mail-From: msmith@cbnco.com X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS, SPF_PASS autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Subject: Recommended way to stage nothing? X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Nov 2010 00:07:24 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, There's a recipe that installs binary blob libraries, overwriting the libraries from a standard package. (Let's say the first letter of the binary recipe is N, second is V...) There is no need to stage the binary libraries; at build-time the standard libraries are fine. What's the best way to prevent anything from being staged in the new post-legacy-staging world? At the moment I'm doing: EXCLUDE_FROM_SHLIBS = "1" sysroot_stage_all() { } Seems to work, but I don't know if it's the right way. Mike