Webkit-gtk3 or webkit-gtk-devel?s

[Jeremy Huddleston Sequoia]

Try this:

Index: Portfile
===================================================================
--- Portfile	(revision 104900)
+++ Portfile	(working copy)
@@ -229,3 +229,19 @@
 livecheck.type  regex
 livecheck.url   http://webkitgtk.org/?page=download
 livecheck.regex webkitgtk-(\[0-9\]+\\.\[0-9\]*\[02468\]\\.\[0-9\]+)
+
+subport webkit-gtk3 {
+    depends_lib-delete \
+        port:gtk2
+
+    depends_lib-append \
+        port:gtk3
+
+    configure.args-delete \
+        --with-gtk=2.0 \
+        --disable-webkit2 \
+
+    configure.args-append \
+        --with-gtk=3.0 \
+        --enable-webkit2 \
+}


On Apr 4, 2013, at 12:42 PM, Eric Gregory <eric at yorba.org> wrote:

> On Wed, Apr 3, 2013 at 3:01 PM, Jeremy Huddleston Sequoia <
> jeremyhu at macports.org> wrote:
> 
>> 
>> You could submit a patch for the Portfile.  I don't use gtk3 so I haven't
>> even tried to build webkit-gtk for gtk3. =).  That's more or less the same
>> story for the +quartz variant of webkit-gtk…
>> 
>> On a related note, if you try using gtk3 with webkit-gtk, I think you
>> should also try --enable-webkit2 if it's not on by default.  I seem to
>> recall that it required gtk3.
>> 
> 
> Some good news: just by changing the portfile to require Gtk3 and setting
> WebKitGtk to build with Gtk3 was all it took.  It built perfectly fine and
> our app is now up and running.  I can send a patch if you like, but it's
> literally a two character change.
> 
> That said, I didn't try enabling the new webkit2 as I'm not using it.  But
> from the other thread it sounds like that may be packaged separately anyhow.
> 
> - Eric

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4145 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20130404/b2f99c91/attachment-0001.p7s>