[QGIS-trac] Re: [Quantum GIS] #2785: [Cmake] FindGRASS.cmake issue

[Quantum GIS]

#2785: [Cmake] FindGRASS.cmake issue
-------------------------------------+--------------------------------------
        Reporter:  vesnikos          |         Owner:  nobody       
            Type:  enhancement       |        Status:  closed       
        Priority:  minor: annoyance  |     Milestone:  Version 1.6.0
       Component:  Build/Install     |       Version:  Trunk        
      Resolution:  invalid           |      Keywords:               
Platform_version:                    |      Platform:  Debian       
        Must_fix:  No                |   Status_info:  1            
-------------------------------------+--------------------------------------
Changes (by vesnikos):

  * status:  new => closed
  * type:  bug => enhancement
  * resolution:  => invalid


Comment:

 Should have closed that bug ages ago.

 Problem lies that in clarification in the documentation: Nowhere states
 that qgis is NOT compatible with grass70 - just says GRASS, no version

 The another issued thats needs confirmation (its been couple of weeks
 since i've tested it) is that GRASS_PREFIX is not being refreshed if you
 install another version of grass (maybe grass6RC6, after grass70svn) with
 the correct path. Not even a conflict error. Maybe if there are more than
 one grass installations, user should choose manually the path?

 and the third and most major: The grass60RC6 package that comes from
 ubuntus' ubuntugis/unstable ppa is not compatible with qgis to be build
 with grass support. I had to compile from source to get grass support.

 Imho findgrass.cmake is a bit hackish, and needs some love to become more
 robust.
 Since qgis comes to be the frontend of grass, its a shame people to
 stumble in such annoyances

 I'll close the bug, and I hope none took offence in the comments above.

-- 
Ticket URL: <https://trac.osgeo.org/qgis/ticket/2785#comment:11>
Quantum GIS <http://qgis.org>
Quantum GIS is an Open Source GIS viewer/editor supporting OGR, PostGIS, and GRASS formats