Changes between Version 106 and Version 107 of pkg-grass
- Timestamp:
- 01/02/16 03:54:38 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
pkg-grass
v106 v107 22 22 * A desktop raster/vector GIS system (command line and graphical user interface) 23 23 * Main site: http://grass.osgeo.org/ 24 * The available interfaces are the new wxPython GUI ([http://grass.osgeo.org/grass64/manuals/wxGUI.html wxGUI]), the older !Tcl/Tk GUI ([http://grass.osgeo.org/grass64/manuals/gis.m.html GIS.m]), and a plain text curses DOS box command prompt (DOS box has no access to display monitors).25 24 * '''First time users should explore the [http://grass.osgeo.org/documentation/first-time-users/ first steps tutorial]''' after installing. 26 25 27 26 === Installation === 28 * Get the [http://download.osgeo.org/osgeo4w/osgeo4w-setup.exe OSGeo4W Installer]. (''400k network-installer, full download is approx 60-80mb'')27 * Get the OSGeo4W Installer [http://download.osgeo.org/osgeo4w/osgeo4w-setup-x86.exe 32bit] or [http://download.osgeo.org/osgeo4w/osgeo4w-setup-x86_64.exe 64bit]. (''400k network-installer, full download is approx 60-80mb'') 29 28 * Generic installer help can be found on the main [WikiStart OSGeo4W] wiki page. 30 29 * Choose '''grass''' package from ''Desktop'' section. … … 41 40 * Start the osgeo4w shell. Then type: 42 41 {{{ 43 grass 64-text42 grass70 -text 44 43 }}} 45 44 … … 47 46 * Start the osgeo4w shell. Then type: 48 47 {{{ 49 grass 64-gui48 grass70 -gui 50 49 }}} 51 52 Alternatively from the !Tcl/Tk GUI go to `Config -> GRASS working environment -> Change settings -> GRASS variable to set -> "GRASS_GUI=wxpython"`53 If it doesn't work, make sure that python is in the path.54 50 55 51 === Later Installation Update === … … 64 60 * and [http://blog.qgis.org/node/124 Unattended install of QGIS (et al) from OSGeo4W] 65 61 66 * see also the non-OSGeo4W [http://grass.osgeo.org/grass 64/binary/mswindows/native/ stand alone installer] for WinGRASS62 * see also the non-OSGeo4W [http://grass.osgeo.org/grass70/binary/mswindows/native/ stand alone installer] for WinGRASS 67 63 68 64 == TODO == … … 73 69 74 70 * While the GRASS libraries and modules are typically extremely well tested and stable, this new Windows install package is not. Because we are very confident in the underlying GIS code we hope that any problems due to the new Windows packaging efforts will be superficial and quickly resolved. You can help this process by reporting bugs: if it seems to be the fault of the installer report bugs to the [http://trac.osgeo.org/osgeo4w/report OSGeo4W bug tracker], if it seems to be the fault of GRASS, report bugs to the [http://trac.osgeo.org/grass/report GRASS bug tracker]. You will need to create yourself an [http://www.osgeo.org/osgeo_userid/ OSGeo ID] to submit and comment on bugs. Bugs don't get fixed unless people point them out! It is expected that some issues related to spaces in the path names still exist, but we hope to have found most of these by now. Also it is likely that the wxPython GUI still has some gremlins in it, please help us find and fix them by reporting any errors you come across! Typically once found they are easy to fix. You can help to find spaces-in-the-path bugs by installing OSGeo4W into "`Program Files\OSGeo4W`" and setting the GRASS data directory to "`Documents and Settings\username`". 75 76 * If a bunch of errors appear in the DOS command window (e.g. "Traceback ... wxgui.py, line 1234") you can cut and paste these to a text file or bug report by right-clicking on the window and selecting "Mark". Scroll up to the top of the text and drag the highlight box down over the text with the left mouse button. When you are done highlighting right click. You can then Paste the text from the clipboard.77 78 * GRASS "monitors" are not present in this build due to an unresolved [http://article.gmane.org/gmane.comp.gis.grass.devel/18751/ problem replacing] [http://article.gmane.org/gmane.comp.gis.grass.devel/24221/ Unix-domain sockets] [http://article.gmane.org/gmane.comp.gis.grass.devel/25688/ with pipes or TCP sockets] and so some interactive modules which require them, such as i.class and i.ortho.photo, will not work. You will need to use a Cygwin build for Windows to use those modules or help port them to the new multi-platform wxPython GUI.79 71 80 72 * See also [https://trac.osgeo.org/grass/wiki/CompileOnWindows#Errata keyword: wingrass tickets in the main GRASS bug tracker] … … 92 84 [[TicketQuery(status=closed&keywords~=grass&order=priority)]] 93 85 94 95 86 == Packager Notes == 96 87 97 88 * Compile guide: [http://trac.osgeo.org/grass/wiki/CompileOnWindows Build using MinGW] see also support scripts from [http://svn.osgeo.org/grass/grass-addons/tools/wingrass-packager/ SVN] 98 89 * Main WinGRASS [http://grass.osgeo.org/wiki/WinGRASS_Current_Status project current status] page 99 * Steps:100 * compile GRASS in a way that it fits in the OSGeo4W directory hierarchy.[[BR]]Example: [http://trac.osgeo.org/grass/browser/grass/branches/develbranch_6/mswindows/osgeo4w/package.sh]101 * OSGeo4W package is created in `mswindows\osgeo4w\package`102 * Depends on the [wiki:pkg-msys MSYS/MinGW] package for command line operations, because GRASS 6 uses unix shell scripts (GRASS 7 uses Python and so no UNIX compatibility is needed at run time [but build scripts still require GNU tools like awk, sed, etc.])103 * WinGRASS is built with MSYS/MinGW. The libraries used to link to the VC++ built GDAL & friends is in the mingw-libs package (copies of the libraries: ''foo''{{{.lib}}} renamed to {{{lib}}}''foo''{{{.a}}}).104 * Release tree: http://download.osgeo.org/osgeo4w/release/grass/ (the installer selects the package with highest version number)105 90 * Maintainer: [wiki:MartinLanda Martin Landa] 106 91 <!-- 107 92 === Package: `msys-grass` === 108 93 … … 123 108 124 109 3. Unpack into `C:\OSGeo4W\bin` 110 -->