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 1QBhsp-0006hm-Cx for openembedded-core@lists.openembedded.org; Mon, 18 Apr 2011 08:24:27 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id p3I6M8ET008927; Mon, 18 Apr 2011 07:22:08 +0100 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 08873-01; Mon, 18 Apr 2011 07:22:04 +0100 (BST) 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 p3I6M1as008921 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Apr 2011 07:22:02 +0100 From: Richard Purdie To: openembedded-core Date: Mon, 18 Apr 2011 07:21:53 +0100 Message-ID: <1303107713.5518.49.camel@rex> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Virus-Scanned: amavisd-new at rpsys.net Cc: "poky@yoctoproject.org" Subject: Shared work directory proof of concept 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: Mon, 18 Apr 2011 06:24:27 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit One of the items on the 1.1 feature list is sharing work directories. This is desirable for example for gcc where the same sources are unpacked and patched for gcc-cross-initial, gcc-cross-intermediate, gcc-cross, gcc-runtime and so on. I've done a little experimentation with this and the code linked to below shows its at least possible and the kind of changes we might need to make to bitbake to support it: http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie/gcc-sharedwork&id=4a22c2212466ef3bcb20960b1f99f8509347b24d There are at least 4 issues I've noted in the commit which we'd need to to look before we could start using this code, nothing impossible though, just needs more work. Cheers, Richard