Bug 121704

Summary: [GTK] Enable the Wayland target if GTK+ dependency is found
Product: WebKit Reporter: Zan Dobersek <zan>
Component: New BugsAssignee: Zan Dobersek <zan>
Status: RESOLVED FIXED    
Severity: Normal CC: gustavo, mrobinson
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 121703, 121787    
Bug Blocks:    
Attachments:
Description Flags
Patch gustavo: review+

Zan Dobersek
Reported 2013-09-20 12:33:49 PDT
[GTK] Enable the Wayland target if GTK+ dependency is found
Attachments
Patch (4.03 KB, patch)
2013-09-20 12:40 PDT, Zan Dobersek 		gustavo: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Zan Dobersek
Comment 1 2013-09-20 12:34:47 PDT
Analogous to r155899 which was only applied to the 2.2 branch. http://trac.webkit.org/changeset/155899
Zan Dobersek
Comment 2 2013-09-20 12:40:46 PDT
Created attachment 212208 [details] Patch
Gustavo Noronha (kov)
Comment 3 2013-09-23 05:47:41 PDT
Comment on attachment 212208 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=212208&action=review > Source/autotools/Versions.m4:20 > +m4_define([gtk3_wayland_required_version], [3.9.14]) Is this satisfied by the jhbuild-wayland.modules we added? If not, mind bumping the version there? I think it would make sense.
Zan Dobersek
Comment 4 2013-09-23 07:34:08 PDT
Comment on attachment 212208 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=212208&action=review >> Source/autotools/Versions.m4:20 >> +m4_define([gtk3_wayland_required_version], [3.9.14]) > > Is this satisfied by the jhbuild-wayland.modules we added? If not, mind bumping the version there? I think it would make sense. Sure, bug #121787. Mind if I bump to 3.9.16 and set that version as a requirement here? That's what I've been using for the past week since it's provided by the GNOME3 ppa.
Zan Dobersek
Comment 5 2013-09-24 06:13:24 PDT
Committed r156328: <http://trac.webkit.org/changeset/156328>
Note You need to log in before you can comment on or make changes to this bug.