From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga03.intel.com ([143.182.124.21]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1UYiNA-0001lY-Hi for openembedded-core@lists.openembedded.org; Sat, 04 May 2013 21:43:59 +0200 Received: from azsmga002.ch.intel.com ([10.2.17.35]) by azsmga101.ch.intel.com with ESMTP; 04 May 2013 12:25:58 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,612,1363158000"; d="scan'208";a="236867139" Received: from unknown (HELO envy2.home) ([10.255.12.120]) by AZSMGA002.ch.intel.com with ESMTP; 04 May 2013 12:25:57 -0700 Message-ID: <518560C5.2050703@linux.intel.com> Date: Sat, 04 May 2013 12:25:57 -0700 From: Darren Hart User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Paul Eggleton References: <1367622401-28624-1-git-send-email-sgw@linux.intel.com> <5184753F.9010904@linux.intel.com> <3611267.eqIsdCBgi9@helios> In-Reply-To: <3611267.eqIsdCBgi9@helios> X-Enigmail-Version: 1.5.1 Cc: openembedded-core@lists.openembedded.org, Scott Rifenbark Subject: Re: [PATCH] dmidecode: fix fetch path to use BP X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 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: Sat, 04 May 2013 19:43:59 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 05/04/2013 01:11 AM, Paul Eggleton wrote: > On Friday 03 May 2013 19:41:03 Darren Hart wrote: >> On 05/03/2013 04:06 PM, Saul Wold wrote: >>> This is so the multilib prefix is not used >> >> Thanks for catching that Saul. How do we know when to use P and when to >> use BP? > > The easiest thing is to imagine what would happen were the recipe to be > BBCLASSEXTENDed to native - would xyz-native make sense where you've used the > reference, or does it always need to be xyz regardless of how it is being > built? If the former, PN (or P with the version); if the latter, BPN (or BP > with the version). > >> Where should this be documented? Maybe in the dev manual for >> writing new recipes? > > It was pointed out recently on IRC that we may need to expand and adjust the > section in the dev manual so it provides more of a step-by-step guide to > creating a recipe, and I plan to work with Scott to do that for this cycle, so > we should be able to include this as part of that. > > Cheers, > Paul Thank you Paul! -- Darren Hart Intel Open Source Technology Center Yocto Project - Technical Lead - Linux Kernel