Bug 1674

Summary: run gtk+ over directfb
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Xiaofeng Yan <Xiaofeng.yan>
Component: coreAssignee: Xiaofeng Yan <Xiaofeng.yan>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: liang.li2, meta.mr.watcher, meta.watcher, sgw, yi.zhao
Version: 1.2   
Target Milestone: 1.2 M1   
Hardware: All   
OS: Multiple   
Whiteboard: (P2) (QA testing completed) Done
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Xiaofeng Yan 2011-10-14 00:44:45 UTC
Create an image including directfb without X and run gtk+ on this image.
Comment 1 Saul Wold 2011-11-21 16:08:29 UTC
Design & Test Plan OK
Comment 2 Saul Wold 2011-11-21 16:08:56 UTC
Design & Test Plan OK
Comment 3 Yi Zhao 2011-11-22 22:22:56 UTC
After discussion with Xiaofeng, QA will try to build a gtk-directfb image and run gtk-demo command to check the correctness of this feature.
So the test plan is ready.
Comment 4 Xiaofeng Yan 2012-01-05 19:27:18 UTC
Patches have been merged into OE-core, waiting for test result.
Comment 5 Yi Zhao 2012-01-11 18:25:32 UTC
Test failed.

Tree/Branch: Poky/master
Poky Commit: 468998cddbe1a803096c9b357e1b5daa3b7e8c2e

Error log:
#############
| checking for CAIRO_BACKEND... no
| configure: error: Package requirements (cairo-xlib >= 1.6) were not met:
| 
| No package 'cairo-xlib' found
| 
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
| 
| Alternatively, you may set the environment variables CAIRO_BACKEND_CFLAGS
| and CAIRO_BACKEND_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
| ERROR: oe_runconf failed
.....

ERROR: '/buildarea2/poky/meta/recipes-gnome/gtk+/gtk+_2.24.8.bb' failed

#####################
Comment 6 Yi Zhao 2012-01-13 00:40:20 UTC
Since this is a feature bug used to track features, I open a new bug 1900 to track the failure. Mark this bug as fixed.
Comment 7 Yi Zhao 2012-01-13 00:40:56 UTC
Mark this bug as fixed.