[GRASS-dev] Re: [GRASS GIS] #943: wxpython gui hangs after switching to cairo display driver

GRASS GIS trac at osgeo.org
Tue Feb 16 00:36:04 EST 2010


#943: wxpython gui hangs after switching to cairo display driver
----------------------+-----------------------------------------------------
  Reporter:  epatton  |       Owner:  grass-dev at lists.osgeo.org   
      Type:  defect   |      Status:  new                         
  Priority:  normal   |   Milestone:  6.5.0                       
 Component:  Display  |     Version:  svn-develbranch6            
Resolution:           |    Keywords:  cairo, driver, gui, wxpython
  Platform:  Linux    |         Cpu:  x86-64                      
----------------------+-----------------------------------------------------
Comment (by glynn):

 Replying to [ticket:943 epatton]:

 > I have compiled Grass 6.5 from a fresh checkout from svn, set --with-
 cairo, --with-cairo-libs=/usr/lib, and --with-cairo-includes=/usr/include.

 You should never need to specify /usr/lib or /usr/include explicitly
 (however, recent versions of GCC will explicitly ignore them, so it's
 harmless).

 On Linux, you should only need --with-cairo, which obtains the compiling
 and linking flags via pkg-config. The --with-cairo-includes, --with-cairo-
 libs, and --with-cairo-ldflags switches are there for platforms lacking
 pkg-config.

 > One thing I just noticed is that the configure line
 >
 {{{
 checking for cairo linking flags...
 }}}
 >
 > appears as it does above, with no confirmation about whether or not it
 found cairo linking flags. But then I'm not sure it it's supposed to print
 anything in a successful case, either.

 It prints whatever you specified for --with-cairo-ldflags. If you didn't
 use it, then it won't print anything.

 If the cairo driver gets built, there's nothing wrong with the configure
 switches. If it doesn't work, that suggests a bug in either the driver or
 the GUI.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/943#comment:4>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list