Bug report #714
WinQGIS: which GRASS version included?
|Affected QGIS version:||Regression?:||No|
|Operating System:||All||Easy fix?:||No|
|Pull Request or Patch supplied:||Resolution:||fixed|
|Crashes QGIS or corrupts data:||Copied to github as #:||10773|
my attempts to figure this out weren't successfull so far. Which GRASS version do you include in the QGIS for Windows version? Please post it there:
http://qgis.org/uploadfiles/testbuilds/ -> README
If other QGIS packages include GRASS, please post also there the version. This is relevant for us since people often report problems to us, too.
#3 Updated by Tim Sutton over 14 years ago
- Resolution set to fixed
- Status changed from Open to Closed
In I have included specifics of grass and other libs used in the windows build in doc/index.html. This page appears under help -> help contents, and as the readme at the end of the installer process. I prefer to do it this way than your suggested way as teh versions are then shipeed with the exe. I have also add a task item to the relase template an example of which you can see at : http://wiki.qgis.org/qgiswiki/ReleaseChecklist0.8.1
In regards to collaboration - yes it would be great to collaborate with GRASS roject on which version to include in the QGIS bundle. Even better Im hoping that we can get binary copy of msys built grass from teh grass project to include in qgis. I think this will be advantageous to both projects - GRASS project can feel comfortable with the quality of the GRASS build being shiped with QGIS and QGIS will be freed up from the time we have to invest in grass specific issues.
Does grass not have a programmatic way to requestion what version number the current build is? It ould be a handy addition which would enable us to dynamically check which grass we have and display the info in qgis help-> about box.
#4 Updated by Markus Neteler over 14 years ago
yes, there is a programmatic way:
include/version.h.in #define GRASS_VERSION_STRING "@(#) @[email protected] (@[email protected])" #define GRASS_VERSION_MAJOR @[email protected] #define GRASS_VERSION_MINOR @[email protected] #define GRASS_VERSION_RELEASE @[email protected]
is expanded through "configure" to
include/version.h #define GRASS_VERSION_STRING "@(#) 6.3.cvs (2007)" #define GRASS_VERSION_MAJOR 6 #define GRASS_VERSION_MINOR 3 #define GRASS_VERSION_RELEASE cvs
Once we have done the migration to SVN, we can atomically track the SVN version number. With CVS unfortunately not possible.
Testing procedure: Here I have accumulated some GRASS tests: