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 1S9nDg-0008J1-K4 for openembedded-core@lists.openembedded.org; Tue, 20 Mar 2012 01:46:36 +0100 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q2K0bZDE004181; Tue, 20 Mar 2012 00:37:35 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 03777-03; Tue, 20 Mar 2012 00:37:27 +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 q2K0bLbd004167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Mar 2012 00:37:22 GMT Message-ID: <1332203843.9740.76.camel@ted> From: Richard Purdie To: Wolfgang Denk Date: Tue, 20 Mar 2012 00:37:23 +0000 In-Reply-To: <20120319215934.5336A206060@gemini.denx.de> References: <20120319215934.5336A206060@gemini.denx.de> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: openembedded-core@lists.openembedded.org Subject: Re: specific version dependenciews - was: Linking two recipes 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: Tue, 20 Mar 2012 00:46:36 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Mon, 2012-03-19 at 22:59 +0100, Wolfgang Denk wrote: > In message <1332192150.9740.72.camel@ted> you wrote: > > On Mon, 2012-03-19 at 13:59 -0700, simran singh wrote: > > > Hello, > > > I have recipes for two applications Recipe A and Recipe B. Recipe B > > > requires a lib.so file and init.h file which are installed by Recipe > > > A. > ... > > recipe B needs to do: > > > > DEPENDS += "recipeA" > > I have a similar, but more complicated requirement which I don;t know > how to implement (if this is possible at all): > > Some MACHINEs require a package A (some library), but in specific > versions: say machine X needs version A-1.2, while machine Y needs > version A-1.5. > > Package A itself depends on another package B (another library). > > The problem is, that different versions of A require specific versions > of B. For example, to build A-1.2 we must use B-4.5, but to build > A-1.5 we must use B-8.2. > > I am aware that I can describe the dependencies at the top leven, > stating for example that machine X needs A-1.2 and B-4.5, while > machine Y needs A-1.5 and B-8.2. > > However, this seems clumsy, as the version depency A->B is something > that is only defined by the implementation of A, and I would like to > keep it encapsulated at this level. > > > Is there a clever way to describe such a multi-level dependency chain? If you mark A and B as machine specific, the system should be able to cope with the problem and set the preferred versions at the machine level. Cheers, Richard