From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from r-finger.com ([178.79.160.5]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1TQaC0-000066-ES for openembedded-core@lists.openembedded.org; Tue, 23 Oct 2012 10:50:32 +0200 Received: from [192.168.0.2] (host81-153-114-169.range81-153.btcentralplus.com [81.153.114.169]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by r-finger.com (Postfix) with ESMTPSA id 0773199A4 for ; Tue, 23 Oct 2012 09:37:07 +0100 (BST) Message-ID: <50865733.40007@r-finger.com> Date: Tue, 23 Oct 2012 09:37:07 +0100 From: Tomas Frydrych User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120624 Icedove/10.0.5 MIME-Version: 1.0 To: openembedded-core@lists.openembedded.org References: <5085800A.4060600@r-finger.com> In-Reply-To: Subject: Re: [RFC] OpenGL packaging/staging policy 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: Tue, 23 Oct 2012 08:50:32 -0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 23/10/12 03:06, Daniel Stone wrote: > What? You can't do that. Well, you kinda can if you're using GLX and > nothing else, maybe, sorta. But the EGL and GL (ES) implementations > are very heavily tied together and can't be used as independent works. > You can separate GLU, which we've already done. I think you can > split out the core of libgbm, but not the DRI plugin. And that's > about it. I am well aware that GL stacks are closely tied together, and personally would not advise anyone to mix and match. But please reread the original email Ross sent explaining the Cedar Trail 'complex' situation. If Intel want to use mesa GL and their PVR GLES1/2 / EGL binary bits together ... Regardless what is done with the packaging, allowing only mesa to stage dev files will break things. GL headers are not interchangeable, even if all the implementers are well behaved (which is a big if), the *platform.h files are allowed to be implementation specific and so have to be staged by the actual platform GL stack. Tomas