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?
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?
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
