[PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[Jacob Stiffler]

* 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-stiffler@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"
 
-- 
1.9.1

[PATCH 2/2] packagegroup-arago-tisdk-addons*: Add opencv

[Jacob Stiffler]

* Add opencv-apps to the filesystem addons
  (packagegroup-arago-tisdk-addons)
* Add opencv-dev to the target devkit
  (packagegroup-arago-tisdk-addons-sdk-target)

Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
---
 .../packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb   | 4 +++-
 .../recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb | 8 +++++++-
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb
index 6322ee8..0165c6d 100644
--- a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb
+++ b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons-sdk-target.bb
@@ -1,6 +1,6 @@
 DESCRIPTION = "Task to install headers and libraries related to addons into the SDK"
 LICENSE = "MIT"
-PR = "r23"
+PR = "r24"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -119,11 +119,13 @@ EXTRA_LIBS_append_k2e-evm = "\
 UTILS_append_omap3 = " canutils-dev"
 UTILS_append_ti33x = " canutils-dev"
 UTILS_append_ti43x = " canutils-dev"
+UTILS_append_omap-a15 = " opencv-dev"
 UTILS_append_dra7xx = " canutils-dev \
                         opencl-staticdev \
                         elfutils-dev \
                         elfutils-staticdev \
 "
+UTILS_append_keystone = " opencv-dev"
 UTILS_append_k2hk-evm = " opencl-staticdev"
 UTILS_append_k2l-evm = " opencl-staticdev"
 UTILS_append_k2e-evm = " opencl-staticdev"
diff --git a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb
index 3ab3bf8..9f941ad 100644
--- a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb
+++ b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisdk-addons.bb
@@ -1,6 +1,6 @@
 DESCRIPTION = "Task to install additional utilities/demos for SDKs"
 LICENSE = "MIT"
-PR = "r41"
+PR = "r42"
 
 PACKAGE_ARCH = "${MACHINE_ARCH}"
 
@@ -102,10 +102,16 @@ EXTRA_PACKAGES = " \
     nodejs-npm \
     protobuf \
 "
+EXTRA_PACKAGES_append_omap-a15 = " \
+    opencv-apps \
+"
 EXTRA_PACKAGES_append_dra7xx = " \
     opencl-staticdev \
     opencl-examples-dev \
 "
+EXTRA_PACKAGES_append_keystone = " \
+    opencv-apps \
+"
 EXTRA_PACKAGES_append_k2hk-evm = " \
     opencl-staticdev \
     opencl-examples-dev \
-- 
1.9.1

Re: [PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[Jacob Stiffler]

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-stiffler@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"
>   

Re: [PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[Denys Dmytriyenko]

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 <j-stiffler@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

Re: [PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[Jacob Stiffler]

[-- Attachment #1: Type: text/plain, Size: 2527 bytes --]



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.


We use the qtwayland component for the GUI in the video analytics demo.

>
>> 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-stiffler@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


[-- Attachment #2: Type: text/html, Size: 24855 bytes --]

Re: [PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[Denys Dmytriyenko]

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-stiffler@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
> 

Re: [PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[Jacob Stiffler]

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-stiffler@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

Re: [PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[Denys Dmytriyenko]

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-stiffler@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
> 

Re: [PATCH 1/2] arago.conf: Remove qtwayland from opencv PACKAGECONFIG for keystone

[Denys Dmytriyenko]

This alters package configuration based on machine/soc w/o making the package 
machine-specific, resulting in a conflict or package rebuild and checksum 
mismatch...

-- 
Denys


On Mon, Feb 15, 2016 at 01:43:13PM -0500, 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-stiffler@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"
>  
> -- 
> 1.9.1
> 
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago