From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gravedo.de ([85.214.79.159]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QJ7br-00042s-Jd for openembedded-devel@lists.openembedded.org; Sun, 08 May 2011 19:17:35 +0200 Received: by gravedo.de (Postfix, from userid 5001) id 85D8C799012; Sun, 8 May 2011 19:14:54 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on h1108419.serverkompetenz.net X-Spam-Level: X-Spam-Status: No, score=-4.2 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from [192.168.178.21] (dslb-088-070-129-150.pools.arcor-ip.net [88.70.129.150]) by gravedo.de (Postfix) with ESMTPSA id 0149D798D6F for ; Sun, 8 May 2011 19:14:53 +0200 (CEST) Message-ID: <4DC6CF8D.5090706@gravedo.de> Date: Sun, 08 May 2011 19:14:53 +0200 From: Simon Busch User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10 MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <1304773638-24877-1-git-send-email-morphis@gravedo.de> <4DC68C80.2040506@gravedo.de> <4DC6CA02.1000009@gravedo.de> In-Reply-To: Subject: Re: [PATCH] qt4-libs-native: add initial recipe 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: Sun, 08 May 2011 17:17:35 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 08.05.2011 18:59, Otavio Salvador wrote: > On Sun, May 8, 2011 at 13:51, Simon Busch wrote: > ... >> Hm, I need it for the embedded variant of qt4 so we should add it to >> qt4.inc which is already quite complex and very target specific. I think >> the best option is to create a qt4-native recipe which provides both >> qt4-tools-native and qt4-libs-native. This would even be the best option >> to be backward compatible (some stuff in OE is depending on >> qt4-native-tools in different versions). > > The native variant does need to be the embedded one for you? I think > you just needed it to run something that uses QtCore or something > similar during the build process (my case) and then build it for the > target. No, the native variant should be build from the qt4 anywhere package as it's already the case for the qt4-tools-native. My qt4-native recipe does this too. It builds only the needed tools and libraries and installs them to the sysroot. Currently it builds: - src/tools/moc - src/corelib - src/xml - src/network - src/tools/uic - src/tools/rcc - src/xmlpatterns - src/testlib - src/qt3support If some other libs/tools are needed for any other native tool we should add it to the list above. And yes, you are right my recipes which need the qt4-native one only needs the Qt4 core libs (as it should be the case for most native stuff which uses qt4). regards, Simon