Well, it would be rather expensive to rebuild opencv for each machine... BTW, in this case having a .bbappend would be more preferable to change PACKAGECONFIG for keystone and set it as machine-speicfic.
-- Denys On Wed, Feb 17, 2016 at 05:18:18PM -0500, Jacob Stiffler wrote: > Should I mark opencv as machine-specific in arago.conf? > > On 2/15/2016 4:02 PM, Denys Dmytriyenko wrote: > >On Mon, Feb 15, 2016 at 03:40:53PM -0500, Jacob Stiffler wrote: > >> > >>On 2/15/2016 2:04 PM, Denys Dmytriyenko wrote: > >>>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? > >>The 3.1 recipe was created by Hongmei and based on > >>http://cgit.openembedded.org/cgit.cgi/meta-openembedded/tree/meta-oe/recipes-support/opencv/opencv_2.4.bb?h=master. > >Well, not exactly. The original 3.0 recipe that we added to meta-arago was > >backported from meta-oe/master as is. > > > >Then, 3.1 update came along and this one is completely custom, as no other > >layer has 3.1 and the dependency on qtwayland is also something that we > >added. > > > > > >>We use the qtwayland component for the GUI in the video analytics demo. > >Ok, by the looks of it, enabling WITH_QT option in opencv allows it to work > >with QT and open windows in opencv-enabled apps... > > > > > >>>>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 <j-stiff...@ti.com> > >>>>>--- > >>>>> 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 > _______________________________________________ meta-arago mailing list meta-arago@arago-project.org http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
