[MacPorts] #29092: clutter should not depend on gtk2

MacPorts noreply at macports.org
Wed Apr 13 11:47:02 PDT 2011


#29092: clutter should not depend on gtk2
-----------------------------------------+----------------------------------
  Reporter:  james.athey@…               |       Owner:  devans@…           
      Type:  enhancement                 |      Status:  closed             
  Priority:  Normal                      |   Milestone:                     
 Component:  ports                       |     Version:  1.9.2              
Resolution:  fixed                       |    Keywords:  haspatch           
      Port:  clutter                     |  
-----------------------------------------+----------------------------------
Changes (by devans@…):

  * status:  assigned => closed
  * resolution:  => fixed


Comment:

 Thanks to all for their input.  Changes committed in r77796.

 My comments:

 The gtk2 dependency is indeed no longer needed.  It was a hold-over from
 from pre-2.22 versions where gdk-pixbuf was included.  Now separate.

 I have not used the quartz backend in the default (x11) configuration as
 suggested because (as jmr points out) the darwin platform category not
 only includes macosx platforms but also darwin platforms that do not have
 access to Quartz (e.g. pure darwin).

 I have re-written the port allowing the +quartz variant only on macosx
 platforms to
 emphasize this.

 Not to say that using the quartz backend on an X11 macosx platform might
 not work but I would suggest that you make a customized port for your
 personal use if you want to do this. The
 clutter developers classify macosx/quartz as experimental as it is.

 Note that the obnoxious behavior of pulling in a bunch of X11 dependencies
 when building
 the +no_x11/+quartz variant was not purely a result of including the
 dependency on gtk2.  It
 came from building the +no_x11 variant against a gtk2/pango built for x11
 (without the +no_x11).

 In general, building +quartz/+no_x11 variants only works when all the
 dependents of the
 target port are built with those variants as well (or at least the ones
 that express those
 variants).  This remains an issue in the current port revision since at
 least pango has
 +no_x11 +quartz variants and should be built so to prevent X11 inclusions.

 In any case, both before and after the current modifications,
 I was able to build clutter +no_x11 +quartz without any X11 ports being
 pulled in using a
 build environment where +quartz +no_x11 are asserted globally.

-- 
Ticket URL: <https://trac.macports.org/ticket/29092#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list