From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bear.ext.ti.com (bear.ext.ti.com [192.94.94.41]) by arago-project.org (Postfix) with ESMTPS id E1C7252982 for ; Mon, 15 Feb 2016 19:05:15 +0000 (UTC) Received: from dflxv15.itg.ti.com ([128.247.5.124]) by bear.ext.ti.com (8.13.7/8.13.7) with ESMTP id u1FJ5EUq019667 for ; Mon, 15 Feb 2016 13:05:14 -0600 Received: from DLEE71.ent.ti.com (dlee71.ent.ti.com [157.170.170.114]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id u1FJ5EKL008673 for ; Mon, 15 Feb 2016 13:05:14 -0600 Received: from dlep32.itg.ti.com (157.170.170.100) by DLEE71.ent.ti.com (157.170.170.114) with Microsoft SMTP Server id 14.3.224.2; Mon, 15 Feb 2016 13:05:14 -0600 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep32.itg.ti.com (8.14.3/8.13.8) with ESMTP id u1FJ5Exd032103; Mon, 15 Feb 2016 13:05:14 -0600 Date: Mon, 15 Feb 2016 14:04:58 -0500 From: Denys Dmytriyenko To: Jacob Stiffler Message-ID: <20160215190458.GG31480@edge> References: <1455561794-2206-1-git-send-email-j-stiffler@ti.com> <56C21EA9.3090209@ti.com> MIME-Version: 1.0 In-Reply-To: <56C21EA9.3090209@ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: meta-arago@arago-project.org Subject: Re: [PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone X-BeenThere: meta-arago@arago-project.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Arago metadata layer for TI SDKs - OE-Core/Yocto compatible List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Feb 2016 19:05:16 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Mon, Feb 15, 2016 at 01:53:29PM -0500, Jacob Stiffler wrote: > This may be more of an RFC as I have some concerns. > > I am concerned with this patch as it adds machine-specific > configuration for opencv, but the recipe is not marked as > machine-specific. > > Will this pose an issue? Yeah, I just replied on this part. > Now I understand that if opencv packaging is done well enough, that > we should still be able to build the qtwayland parts of opencv, but > do not install them in the keystone filesystem so that wayland is > not brought in. However, wayland has a dependency on the ddk, which > is not compatible with keystone machines. Thus the opencv build will > be broken for keystone machines. > > Any suggestions? Quick question - where did 3.1 recipe come from and what exactly qtwayland dependency do? > On 2/15/2016 1:43 PM, Jacob Stiffler wrote: > >* keystone machines do not have a display, hence they do not support > > wayland > >* opencv adds qtwayland support since wayland is in DISTRO_FEATURES > >* Remove qtwayland from opencv PACKAGECONFIG for keystone machines > > > >Signed-off-by: Jacob Stiffler > >--- > > meta-arago-distro/conf/distro/arago.conf | 3 +++ > > 1 file changed, 3 insertions(+) > > > >diff --git a/meta-arago-distro/conf/distro/arago.conf b/meta-arago-distro/conf/distro/arago.conf > >index 325e112..38c7887 100644 > >--- a/meta-arago-distro/conf/distro/arago.conf > >+++ b/meta-arago-distro/conf/distro/arago.conf > >@@ -58,6 +58,9 @@ PACKAGECONFIG_append_pn-qtmultimedia = " gstreamer" > > # Prefer OpenSSL over GnuTLS for curl due to TSU exemptions > > PACKAGECONFIG_pn-curl = "${@bb.utils.contains("DISTRO_FEATURES", "ipv6", "ipv6", "", d)} ssl zlib" > >+# Remove qtwayland from openvcv PACKAGECONFIG for keystone > >+PACKAGECONFIG_remove_pn-opencv_keystone = "qtwayland" > >+ > > # Enable UI and scripting for perf > > PERF_FEATURES_ENABLE ?= "perf-scripting perf-tui" > > _______________________________________________ > meta-arago mailing list > meta-arago@arago-project.org > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago