From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mx1.pokylinux.org (Postfix) with ESMTP id 211714C80594 for ; Fri, 28 Jan 2011 20:32:28 -0600 (CST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 28 Jan 2011 18:32:26 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.60,395,1291622400"; d="scan'208";a="652317914" Received: from unknown (HELO helios.localnet) ([10.255.16.169]) by fmsmga002.fm.intel.com with ESMTP; 28 Jan 2011 18:32:25 -0800 From: Paul Eggleton Organization: Intel Corporation (UK) To: poky@yoctoproject.org Date: Sat, 29 Jan 2011 02:32:14 +0000 User-Agent: KMail/1.13.5 (Linux/2.6.35-24-generic-pae; KDE/4.5.1; i686; ; ) References: <8B09826E-906B-4744-BF64-C5DCF43F3103@dominion.thruhere.net> <201101281721.00110.paul.eggleton@linux.intel.com> In-Reply-To: <201101281721.00110.paul.eggleton@linux.intel.com> MIME-Version: 1.0 Message-Id: <201101290232.15365.paul.eggleton@linux.intel.com> Subject: Re: [PATCH 11/11] qt4: Add meta-toolchain-qte and dependent tasks from OpenEmbedded X-BeenThere: poky@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Poky build system developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jan 2011 02:32:28 -0000 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit On Friday 28 January 2011 17:20:59 Paul Eggleton wrote: > On Friday 28 January 2011 15:47:28 Koen Kooi wrote: > > Op 28 jan 2011, om 16:27 heeft Joshua Lock het volgende geschreven: > > > On Fri, 2011-01-28 at 00:36 +0000, Paul Eggleton wrote: > > >> +#Qt Declarative is new in 4.7, try to include it like this. > > >> +#RRECOMMENDS_${PN} += " \ > > >> +# libqt-embeddeddeclarative4-dev \ > > >> +# " > > > > > > We don't want to include this? > > > > There was a bug in the OE recipes where the declarative stuff was only > > mentioned in the 4.7.1 recipe, so building meta-toolchain-qte would build > > both 4.6.x and 4.7.1. I think I fixed that a few weeks back, so it should > > be safe to include again. > > Am testing that as we speak, if it works I'll include it in v3 of this > patchset which I will try to post very soon. Unfortunately this fails to build when enabled for 4.6.3, so I have removed the lines until the issue can be rectified properly. Cheers, Paul