Also ur missing the patch that removed the qt platform line from the qt env 
script.


> On Mar 5, 2015, at 12:43 PM, Cooper Jr., Franklin <[email protected]> wrote:
> 
> Patchset looks good.
> 
> Personally I would use true/false instead of 0/1 to make things more obvious.
> 
> Unless someone else has a problem with it then I'll leave it up to you.
> 
> 
>> On Mar 5, 2015, at 12:31 PM, Stiffler, Jacob <[email protected]> wrote:
>> 
>> * This falg may be used to exclude wayland/weston from the file system.
>> * QT platform will be set based on this value.
>> * Add processor-sdk band to disable wayland for ti33x and ti43x.
>> 
>> 
>> 
>> Jacob Stiffler (4):
>> arago-prefs: Add WAYLAND_SUPPORT flag.
>> packagegroups: Implement WAYLAND_SUPPORT flag.
>> qtbase: Set qpa based in WAYLAND_SUPPORT flag.
>> branding-processor-sdk: Add processor-sdk brand.
>> 
>> .../conf/distro/include/arago-prefs.inc            |    2 ++
>> .../conf/distro/include/branding-processor-sdk.inc |   34 
>> ++++++++++++++++++++
>> .../packagegroups/packagegroup-arago-qte.bb        |    4 +--
>> .../packagegroup-arago-tisdk-graphics.bb           |    4 +--
>> .../packagegroups/packagegroup-arago-tisdk-qte.bb  |    4 +--
>> .../packagegroups/packagegroup-linaro-tc-test.bb   |    5 +--
>> meta-arago-distro/recipes-qt/qt5/qtbase/qt_env.sh  |    1 -
>> .../recipes-qt/qt5/qtbase_5.4.1.bbappend           |    9 ++++--
>> 8 files changed, 51 insertions(+), 12 deletions(-)
>> create mode 100644 
>> meta-arago-distro/conf/distro/include/branding-processor-sdk.inc
>> 
>> -- 
>> 1.7.9.5
>> 
>> _______________________________________________
>> meta-arago mailing list
>> [email protected]
>> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
> _______________________________________________
> meta-arago mailing list
> [email protected]
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
_______________________________________________
meta-arago mailing list
[email protected]
http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago

Reply via email to