[GRASS-dev] winGRASS 6.3.0RC5 errors

Marco_Pasetti · February 28, 2008, 5:42pm

Hi all,

I just compiled GRASS 6.3.0RC5 on Windows using MinGW; I report the following errors:

grass63.bat doesn’t work! it says:

ERROR: LOCATION_NAME not set

where should I set it?

my grass63.bat is configured as follows:

@echo off
rem #########################################################################
rem #
rem # GRASS Initialization
rem #
rem #########################################################################
rem Environment variables****
rem Uncomment and set the following values if they differ from the indicated default
rem Directory where your .grassrc6 file will be stored
set HOME=%USERPROFILE%
rem Name of the wish (Tk) executable
set GRASS_WISH=wish.exe
rem Path to the shell command
rem (adjust to where you installed msys or another shell)
set GRASS_SH=c:\msys\bin\sh.exe
rem Path to utilities used by some scripts, such as awk, sed, etc
rem (adjust to where you installed msys, gnuwin32, or other similar utilises)
set PATH=%PATH%;c:\msys\bin;c:\msys\lib;c:\devtools\python
rem Path to your web browser
set GRASS_HTML_BROWSER=%PROGRAMFILES%\Mozilla Firefox\firefox.exe
rem Path to the proj files (notably the epsg projection list)
set GRASS_PROJSHARE=c:\msys\local\share\proj
set WINGISBASE=c:\msys\local\grass-6.3.0RC5
“%WINGISBASE%\etc\init.bat” %*

If I start grass63 from MSYS it’s ok, while if I start with -wxpython it says

$ grass63 -wxpython
WELCOME TO GRASS Version 6.3.0RC5 2008

Have at your side all available GRASS tutorials
When working on your location, the following materials
are extremely useful:

A topo map of your area
Current catalog of available computer maps

Check the GRASS webpages for feedback mailinglists and more:
http://www.grass-gis.org
http://grass.osgeo.org
Hit RETURN to continue
Starting GRASS …
Traceback (most recent call last):
File “C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py”, line 688, in
import gui_modules.gcmd as gcmd
File “C:\MSYS\local\grass-6.3.0RC5\etc\wxpython\gui_modules\gcmd.py”, line 38, in
from win32file import ReadFile, WriteFile
ImportError: No module named win32file
Error in GUI startup. If necessary, please
report this error to the GRASS developers.
Switching to text mode now.
Hit RETURN to continue…

Redirection is not supported.
Marco@NOTEBOOKMARCO /usr/local/bin

Thanks for your help

Marco

mlennert · February 28, 2008, 5:58pm

On 28/02/08 18:42, marco.pasetti@alice.it wrote:

Hi all,
I just compiled GRASS 6.3.0RC5 on Windows using MinGW; I report the following errors:
1) grass63.bat doesn't work! it says:
ERROR: LOCATION_NAME not set

From memory I think this is the normal error message you get when you launch grass without an existing .grassrc6 file. Can't you just push OK and then you get to the tcltk startup screen ?

2) If I start grass63 from MSYS it's ok, while if I start with -wxpython it says

Traceback (most recent call last):
  File "C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py", line 688, in <module>
    import gui_modules.gcmd as gcmd
  File "C:\MSYS\local\grass-6.3.0RC5\etc\wxpython\gui_modules\gcmd.py", line 38, in <module>
    from win32file import ReadFile, WriteFile
ImportError: No module named win32file

You have to install pywin32

http://sourceforge.net/projects/pywin32/

Moritz

martinl · February 28, 2008, 6:01pm

Ciao,

2008/2/28, marco.pasetti@alice.it <marco.pasetti@alice.it>:
[snip]

2) If I start grass63 from MSYS it's ok, while if I start with -wxpython it
says

$ grass63 -wxpython
WELCOME TO GRASS Version 6.3.0RC5 2008
   1) Have at your side all available GRASS tutorials
   2) When working on your location, the following materials
      are extremely useful:
      - A topo map of your area
      - Current catalog of available computer maps
   3) Check the GRASS webpages for feedback mailinglists and more:
      http://www.grass-gis.org
      http://grass.osgeo.org
Hit RETURN to continue
Starting GRASS ...
Traceback (most recent call last):
  File "C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py", line 688, in
<module>
    import gui_modules.gcmd as gcmd
  File
"C:\MSYS\local\grass-6.3.0RC5\etc\wxpython\gui_modules\gcmd.py",
line 38, in <module>
    from win32file import ReadFile, WriteFile
ImportError: No module named win32file
Error in GUI startup. If necessary, please
report this error to the GRASS developers.
Switching to text mode now.
Hit RETURN to continue...

hm, not surprising, since win32file is not part of Python windows
package by default (AFAIK). Sorry for ignorance, did you make some
notes somewhere about installation process on Windows, I found [1,2].
It seems to me that after the years I have reason to install Windows
and try to make wxGUI working also here. I just want to avoid
struggling with installation;-)

Regards, Martin

[1] http://grass.gdf-hannover.de/wiki/WinGRASS_Installation
[2] http://grass.gdf-hannover.de/wiki/WinGRASS_Current_Status

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

Marco_Pasetti · February 28, 2008, 8:56pm

OK,

I intalled Python Extensions (pywin32-210.win32-py2.5.exe) for Windows from http://downloads.sourceforge.net/pywin32/pywin32-210.win32-py2.5.exe

Relaunched grass63 -wxpython

Now the new error is:

Starting GRASS …
Traceback (most recent call last):
File “C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py”, line 690, in
GRASSStartUp = StartUp(0)
File “C:\DevTools\Python\Lib\site-packages\wx-2.8-msw-unicode\wx_core.py”, line 7836, in init
self._BootstrapApp()
File “C:\DevTools\Python\Lib\site-packages\wx-2.8-msw-unicode\wx_core.py”, line 7433, in _BootstrapApp
return core.PyApp__BootstrapApp(*args, **kwargs)
File “C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py”, line 674, in OnInit
StartUp = GRASSStartup()
File “C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py”, line 45, in init
self.grassrc = self._read_grassrc()
File “C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py”, line 356, in _read_grassrc
key, val = line.split(“:”)
ValueError: too many values to unpack
Error in GUI startup. If necessary, please
report this error to the GRASS developers.
Switching to text mode now.
Hit RETURN to continue…

Ideas? Suggestions?

Thanks

Marco

Da: grass-dev-bounces@lists.osgeo.org [mailto:grass-dev-bounces@lists.osgeo.org] Per conto di marco.pasetti@alice.it
Inviato: giovedì 28 febbraio 2008 18.43
A: grass-dev@lists.osgeo.org
Oggetto: [GRASS-dev] winGRASS 6.3.0RC5 errors

Hi all,

I just compiled GRASS 6.3.0RC5 on Windows using MinGW; I report the following errors:

grass63.bat doesn’t work! it says:

ERROR: LOCATION_NAME not set

where should I set it?

my grass63.bat is configured as follows:

@echo off
rem #########################################################################
rem #
rem # GRASS Initialization
rem #
rem #########################################################################
rem Environment variables****
rem Uncomment and set the following values if they differ from the indicated default
rem Directory where your .grassrc6 file will be stored
set HOME=%USERPROFILE%
rem Name of the wish (Tk) executable
set GRASS_WISH=wish.exe
rem Path to the shell command
rem (adjust to where you installed msys or another shell)
set GRASS_SH=c:\msys\bin\sh.exe
rem Path to utilities used by some scripts, such as awk, sed, etc
rem (adjust to where you installed msys, gnuwin32, or other similar utilises)
set PATH=%PATH%;c:\msys\bin;c:\msys\lib;c:\devtools\python
rem Path to your web browser
set GRASS_HTML_BROWSER=%PROGRAMFILES%\Mozilla Firefox\firefox.exe
rem Path to the proj files (notably the epsg projection list)
set GRASS_PROJSHARE=c:\msys\local\share\proj
set WINGISBASE=c:\msys\local\grass-6.3.0RC5
“%WINGISBASE%\etc\init.bat” %*

If I start grass63 from MSYS it’s ok, while if I start with -wxpython it says

$ grass63 -wxpython
WELCOME TO GRASS Version 6.3.0RC5 2008

Have at your side all available GRASS tutorials
When working on your location, the following materials
are extremely useful:

A topo map of your area
Current catalog of available computer maps

Check the GRASS webpages for feedback mailinglists and more:
http://www.grass-gis.org
http://grass.osgeo.org
Hit RETURN to continue
Starting GRASS …
Traceback (most recent call last):
File “C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py”, line 688, in
import gui_modules.gcmd as gcmd
File “C:\MSYS\local\grass-6.3.0RC5\etc\wxpython\gui_modules\gcmd.py”, line 38, in
from win32file import ReadFile, WriteFile
ImportError: No module named win32file
Error in GUI startup. If necessary, please
report this error to the GRASS developers.
Switching to text mode now.
Hit RETURN to continue…

Redirection is not supported.
Marco@NOTEBOOKMARCO /usr/local/bin

Thanks for your help

Marco

Glynn_Clements1 · February 28, 2008, 10:33pm

Marco Pasetti wrote:

File "C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py", line 356, in
_read_grassrc
key, val = line.split(":")
ValueError: too many values to unpack

This should be changed to:

key, val = line.split(":", 1)

The code only expects to find a single colon in each line, separating
the key and the value. But the value itself may contain a colon; in
particular, GISDBASE on Windows will contain a colon after the drive
letter.

--
Glynn Clements <glynn@gclements.plus.com>

martinl · February 28, 2008, 11:15pm

Hi,

2008/2/28, Glynn Clements <glynn@gclements.plus.com>:

Marco Pasetti wrote:

> File "C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py", line 356, in
> _read_grassrc
> key, val = line.split(":")
> ValueError: too many values to unpack

Glynn:

This should be changed to:

key, val = line.split(":", 1)

The code only expects to find a single colon in each line, separating
the key and the value. But the value itself may contain a colon; in
particular, GISDBASE on Windows will contain a colon after the drive
letter.

fixed in trunk

http://trac.osgeo.org/grass/changeset/30396

will be backported to releasebranch_6_3 before releasing 6.3.0. Marco,
can you try to use grass_trunk for testing on Windows?

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

Marco_Pasetti · February 29, 2008, 12:03am

Hi,

can you try to use grass_trunk for testing on Windows?

Sure. But, sorry, not immediately; I'm trying to build a "full working"
version of GRASS + QGIS and, at the same time, write the relative building
guide. Now I need my PC to build QGIS and prepare a selfcontained installer
of GRASS and QGIS (separately); then I'll work on trunk... Working with a 3
years old PC, using MinGW over Windows, makes buildings very, very slow
(GRASS takes about 2,5 hours to compile!!... And meanwhile the PC is quite
unusable)

What do you think about my guide?

Goodnight,

Marco

-----Messaggio originale-----
Da: Martin Landa [mailto:landa.martin@gmail.com]
Inviato: venerdì 29 febbraio 2008 0.15
A: Glynn Clements
Cc: Marco Pasetti; grass-dev@lists.osgeo.org
Oggetto: Re: R: [GRASS-dev] winGRASS 6.3.0RC5 errors

Hi,

2008/2/28, Glynn Clements <glynn@gclements.plus.com>:

Marco Pasetti wrote:

> File "C:/MSYS/local/grass-6.3.0RC5/etc/wxpython/gis_set.py", line

356, in

> _read_grassrc
> key, val = line.split(":")
> ValueError: too many values to unpack

Glynn:

This should be changed to:

key, val = line.split(":", 1)

The code only expects to find a single colon in each line, separating
the key and the value. But the value itself may contain a colon; in
particular, GISDBASE on Windows will contain a colon after the drive
letter.

fixed in trunk

http://trac.osgeo.org/grass/changeset/30396

will be backported to releasebranch_6_3 before releasing 6.3.0. Marco, can
you try to use grass_trunk for testing on Windows?

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

mlennert · February 29, 2008, 8:45am

Hi Marco,

On 28/02/08 23:12, marco.pasetti@alice.it wrote:

Hi Moritz,
>Try erasing your .grassrc6 file and see what happens.
It worked! Thanks... But why that??? Mah...

A corrupt .grassrc6 file can lead to errors. Don't know what happens on the other OS's in that case...

Then I have other (actually stupid) questions:
1) why the last line of grass63.bat is "%WINGISBASE%\etc\init.bat" %* and not "%WINGISBASE%\etc\init.bat" ? What is the last %* ?

This serves to pass on any command line parameters you call the grass63.bat with.

2) in /src/grass-6.3.0RC5/dist.i686-pc-mingw32 I have more files than in /local/grass-6.3.0RC5
the more I have is: GPL.txt, AUTHORS, COPYING, README, grass63.tmp and REQUIREMENTS.html
should I use this folder to prepare a redistributable package?

I don't think you need the grass63.tmp (don't even know why it's there), and the README and REQUIREMENTS.html are about compiling from source. I think that for a binary package only AUTHORS, COPYING and GPL.txt are necessary.

This said, if we start to officially distribute binary packages with the libraries included, we also have to make the source code of all these libraries (and obvioiusly of GRASS) available...

3) what about wx errors?

Glynn already answered this.

I'm preparing a personal winGRASS + QGIS building guide (probably I will also add it to my thesis, as an additional document... I did it... I add it... just for the work I done...); if you want to give it a look and tell me if you find it interesting, even if it's still a WIP... http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html

I think it is very helpful. Could you please either integrate the information into the Wiki or at least link to the page from the wiki ?

One question: when you rebuild gdal --with-grass, the configure output still says "GRASS support: no". Is this normal ?

And would you be willing to make the entire package of binaries of the build dependencies of GRASS available, in replacement of Paul's quite old package ? I don't think he would mind...
Personally, I don't have the time to build this environment (although it should be fairly quick with your instructions).

And do you want to take over the regular building of winGRASS packages ? I have fallen behind the initially desired schedule of recompiling the latest svn-tree once a week... This said, maybe a cron job could do the trick...

Best wishes,

Moritz

Marco_Pasetti · March 1, 2008, 11:55am

Hi,

I decided to change the subject of the mail to a better one, and then to
send the mail to the list, as I should have done before (sorry for the
mistake). Let we start from this:

I think that if you could provide the binary package plus a directory which

contains all the source tarballs you used

and your compilation information, this would be perfect. If you rather have

me host these files, I can do so as well.

If you can, then that's perfect and I "officially" pass on the

responsibility for maintaining the windows binary packages (cc to Markus for
info).

I will obviously continue to help you and try to debug whenever possible. I

have started to add some ToDo's on the Wingrass Status wiki page.

This is probably the best place to keep track of what still needs to be

done.

So, as soon as your package of libraries (and header files) is ready, could

you let me know where I can get it,

so that I can adapt my build system to that ?

I'm very excited about that, that is officially contribute to a such
important family ...but it's the first time for me (I mean about
software releasing and all things related), so I guess that I need to learn
some things before...
That's my questions:

For an user-oriented self installer:

1. because I added some extra-supports in GRASS (such as PostgreSQL, SQLite
and ActiveTcl), I could use Dependency Walker to securely check what files
are needed and then add them in ../bin dir, in order to prepare a self
contained package/installer, whitout the need of asking the user to install
other pieces of software; but, can I do that (I mean about licenses,
permissions, and so on...)? About PostgreSQL and SQLite I rebuilt packages
from source, while about ActiveTcl I used prebuit windows installer.

2. since the new wxPython GUI still doesn't work on windows (for RC05, I'll
check on trunk in the next days), I think that we can avoid to include it in
the RC05 package as requirement; why tell the user to install Python and
wxPython if the new GUI doesn't work?

3. do we really need MSYS? Quantum GIS self installer still have MSYS inside
(only few files), whithout the need of installing it separately. Can we do
do the same?

For development-oriented package:

I thought about the following options:

1. pack all the MSYS "local" folder, excluding sources; all the applications
and libraries included has been built by source with MSYS/MinGW, excluding
Flex and Bison, for which I used prebuilt binaries packages from sourceforge
GNUWin32 Project;

2. pack all the MSYS "local" folder, including sources for all the
libraries/applications built;

3. pack all the MSYS environment, including MinGW installation, "local"
folder and sources; actually, I think that both MSYS and MinGW don't need to
be installed from related installers, you can just copy all the MSYS folder
to your local hard drive.

While for the compilation information i could:

1. add a pdf print of the html guide
2. add a simple text (txt) copy of the html guide

Sounds perfect. You can put the link here:
http://grass.gdf-hannover.de/wiki/Compile_and_Install#MS-Windows.2Fnative
and we could erase this part
http://grass.gdf-hannover.de/wiki/WinGRASS_Current_Status#Compiling_by_your

self

and just link to the previous wiki page.

So I'll need to subscribe, log-in, delete previous entries and the simply
add a "... see here for instructions" link?

Marco

martinl · March 1, 2008, 12:59pm

Ciao Marco,

2008/3/1, Marco Pasetti <marco.pasetti@alice.it>:

[snip]

2. since the new wxPython GUI still doesn't work on windows (for RC05, I'll
check on trunk in the next days), I think that we can avoid to include it in
the RC05 package as requirement; why tell the user to install Python and
wxPython if the new GUI doesn't work?

right now I am following your great installation guide, then I will
try to make wxGUI working on Windows too (basic features for now).
Without functional wxGUI doesn't make sense to require at least
wxPython, Python maybe because of SWIG interface.

[snip]

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

Marco_Pasetti · March 1, 2008, 1:37pm

Hi Martin,

Be careful with the guide, it's still a WIP: refresh it regularly, updates
are on the road... (even if I think that GRASS section is almost complete)

Related to this (the guide): what do you think about keeping GRASS + Quantum
GIS building guide together? Actually some things (like expat, geos and gsl)
are not needed by GRASS, but they are for QGIS. Should I prepare two
different documents, one for GRASS only and one for both GRASS and QGIS
(since I actually don't see great utility of using QGIS without GRASS
plugin, which is instead a great feature of QGIS, specially for not advanced
users)?

PS: thanks for the "great"

-----Messaggio originale-----
Da: Martin Landa [mailto:landa.martin@gmail.com]
Inviato: sabato 1 marzo 2008 14.00
A: Marco Pasetti
Cc: GRASS Developer Mailing List
Oggetto: Re: [GRASS-dev] New Binary Package Project for winGRASS

Ciao Marco,

2008/3/1, Marco Pasetti <marco.pasetti@alice.it>:

[snip]

2. since the new wxPython GUI still doesn't work on windows (for
RC05, I'll check on trunk in the next days), I think that we can
avoid to include it in the RC05 package as requirement; why tell the
user to install Python and wxPython if the new GUI doesn't work?

right now I am following your great installation guide, then I will try to
make wxGUI working on Windows too (basic features for now).
Without functional wxGUI doesn't make sense to require at least wxPython,
Python maybe because of SWIG interface.

[snip]

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

martinl · March 1, 2008, 1:44pm

Hi,

2008/3/1, Marco Pasetti <marco.pasetti@alice.it>:

Related to this (the guide): what do you think about keeping GRASS + Quantum
GIS building guide together? Actually some things (like expat, geos and gsl)
are not needed by GRASS, but they are for QGIS. Should I prepare two
different documents, one for GRASS only and one for both GRASS and QGIS

maybe it would be better, or at least to make note like "this package
is required for GRASS compilation", etc.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

Marco_Pasetti · March 1, 2008, 2:55pm

Hi,

maybe it would be better, or at least to make note like "this package is

required for GRASS compilation", etc.

Ok. I'll do that later, before to release the final version.

What about GEOS, GSL and Expat? Actually, GRASS uses none of them, but GDAL
uses GEOS, I'm not sure if it uses GSL (even if I think not) and it would
use Expat ...if I could be able to enable that support in GDAL

So, summarizing, for the GRASS guide only, should I remove GSL, Expat and
GEOS or leave only GEOS?

Marco

-----Messaggio originale-----
Da: Martin Landa [mailto:landa.martin@gmail.com]
Inviato: sabato 1 marzo 2008 14.44
A: Marco Pasetti
Cc: GRASS Developer Mailing List
Oggetto: Re: R: [GRASS-dev] New Binary Package Project for winGRASS

Hi,

2008/3/1, Marco Pasetti <marco.pasetti@alice.it>:

Related to this (the guide): what do you think about keeping GRASS +
Quantum GIS building guide together? Actually some things (like
expat, geos and gsl) are not needed by GRASS, but they are for QGIS.
Should I prepare two different documents, one for GRASS only and one
for both GRASS and QGIS

maybe it would be better, or at least to make note like "this package is
required for GRASS compilation", etc.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

Benjamin_Ducke3 · March 1, 2008, 8:39pm

Marco Pasetti wrote:

Hi,

maybe it would be better, or at least to make note like "this package is

required for GRASS compilation", etc.

Ok. I'll do that later, before to release the final version.

What about GEOS, GSL and Expat? Actually, GRASS uses none of them, but GDAL
uses GEOS, I'm not sure if it uses GSL (even if I think not) and it would

Only QGIS uses GSL for the georeferencer plugin.

use Expat ...if I could be able to enable that support in GDAL

For what?

So, summarizing, for the GRASS guide only, should I remove GSL, Expat and
GEOS or leave only GEOS?

Only GEOS seems to make sense to me.

Benjamin

Marco

-----Messaggio originale-----
Da: Martin Landa [mailto:landa.martin@gmail.com] Inviato: sabato 1 marzo 2008 14.44
A: Marco Pasetti
Cc: GRASS Developer Mailing List
Oggetto: Re: R: [GRASS-dev] New Binary Package Project for winGRASS

Hi,

2008/3/1, Marco Pasetti <marco.pasetti@alice.it>:

Related to this (the guide): what do you think about keeping GRASS + Quantum GIS building guide together? Actually some things (like expat, geos and gsl) are not needed by GRASS, but they are for QGIS. Should I prepare two different documents, one for GRASS only and one for both GRASS and QGIS

maybe it would be better, or at least to make note like "this package is
required for GRASS compilation", etc.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
Johanna-Mestorf-Straße 2-6
D 24098 Kiel
Germany

Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg

Benjamin_Ducke3 · March 1, 2008, 8:45pm

Marco Pasetti wrote:

1. because I added some extra-supports in GRASS (such as PostgreSQL, SQLite
and ActiveTcl), I could use Dependency Walker to securely check what files
are needed and then add them in ../bin dir, in order to prepare a self
contained package/installer, whitout the need of asking the user to install
other pieces of software; but, can I do that (I mean about licenses,
permissions, and so on...)? About PostgreSQL and SQLite I rebuilt packages
from source, while about ActiveTcl I used prebuit windows installer.

Why use ActiveTcl? The regular, GPL'd Tcl compiles without any problems
and can be distributed freely. Would also be interesting to know how
8.5 is working on Win.

3. do we really need MSYS? Quantum GIS self installer still have MSYS inside
(only few files), whithout the need of installing it separately. Can we do
do the same?

Yes, please. The sh interpreter is vastly superior to cmd.exe.

--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
Johanna-Mestorf-Straße 2-6
D 24098 Kiel
Germany

Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg

Marco_Pasetti · March 1, 2008, 9:03pm

OK

PS: Expat is for XML

Marco

-----Messaggio originale-----
Da: grass-dev-bounces@lists.osgeo.org
[mailto:grass-dev-bounces@lists.osgeo.org] Per conto di Benjamin Ducke
Inviato: sabato 1 marzo 2008 21.40
Cc: 'GRASS Developer Mailing List'
Oggetto: Re: R: R: [GRASS-dev] New Binary Package Project for winGRASS

Marco Pasetti wrote:

Hi,

maybe it would be better, or at least to make note like "this package
is

required for GRASS compilation", etc.

Ok. I'll do that later, before to release the final version.

What about GEOS, GSL and Expat? Actually, GRASS uses none of them, but
GDAL uses GEOS, I'm not sure if it uses GSL (even if I think not) and
it would

Only QGIS uses GSL for the georeferencer plugin.

use Expat ...if I could be able to enable that support in GDAL

For what?

So, summarizing, for the GRASS guide only, should I remove GSL, Expat
and GEOS or leave only GEOS?

Only GEOS seems to make sense to me.

Benjamin

Marco

-----Messaggio originale-----
Da: Martin Landa [mailto:landa.martin@gmail.com]
Inviato: sabato 1 marzo 2008 14.44
A: Marco Pasetti
Cc: GRASS Developer Mailing List
Oggetto: Re: R: [GRASS-dev] New Binary Package Project for winGRASS

Hi,

2008/3/1, Marco Pasetti <marco.pasetti@alice.it>:

Related to this (the guide): what do you think about keeping GRASS +
Quantum GIS building guide together? Actually some things (like
expat, geos and gsl) are not needed by GRASS, but they are for QGIS.
Should I prepare two different documents, one for GRASS only and one
for both GRASS and QGIS

maybe it would be better, or at least to make note like "this package
is required for GRASS compilation", etc.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
*

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel Johanna-Mestorf-Straße 2-6 D 24098
Kiel Germany

Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Marco_Pasetti · March 1, 2008, 9:14pm

Hi Benjamin,

Why use ActiveTcl? The regular, GPL'd Tcl compiles without any problems and

can be distributed freely.

Good question! When I planned the work I dind't considered this option,
because on the wiki it was (it is) suggested to use ActiveTcl;
Probably I should reconsider to build Tcl/Tk from source using MinGW, and
then rebuild GRASS...

Moritz, what do you think about?

Would also be interesting to know how
8.5 is working on Win.

AFAIK there are some problems for GRASS with 8.5, I read it in the list in
the last weeks.

Marco

-----Messaggio originale-----
Da: grass-dev-bounces@lists.osgeo.org
[mailto:grass-dev-bounces@lists.osgeo.org] Per conto di Benjamin Ducke
Inviato: sabato 1 marzo 2008 21.45
Cc: GRASS Developer Mailing List
Oggetto: Re: [GRASS-dev] New Binary Package Project for winGRASS

Marco Pasetti wrote:

1. because I added some extra-supports in GRASS (such as PostgreSQL,
SQLite and ActiveTcl), I could use Dependency Walker to securely check
what files are needed and then add them in ../bin dir, in order to
prepare a self contained package/installer, whitout the need of asking
the user to install other pieces of software; but, can I do that (I
mean about licenses, permissions, and so on...)? About PostgreSQL and
SQLite I rebuilt packages from source, while about ActiveTcl I used

prebuit windows installer.

Why use ActiveTcl? The regular, GPL'd Tcl compiles without any problems and
can be distributed freely. Would also be interesting to know how
8.5 is working on Win.

3. do we really need MSYS? Quantum GIS self installer still have MSYS
inside (only few files), whithout the need of installing it
separately. Can we do do the same?

Yes, please. The sh interpreter is vastly superior to cmd.exe.

--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel Johanna-Mestorf-Straße 2-6 D 24098
Kiel Germany

Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg

_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

martinl · March 2, 2008, 1:43pm

Hi,

2008/3/1, Martin Landa <landa.martin@gmail.com>:
Marco:

> 2. since the new wxPython GUI still doesn't work on windows (for RC05, I'll
> check on trunk in the next days), I think that we can avoid to include it in
> the RC05 package as requirement; why tell the user to install Python and
> wxPython if the new GUI doesn't work?

Martin:

right now I am following your great installation guide, then I will
try to make wxGUI working on Windows too (basic features for now).
Without functional wxGUI doesn't make sense to require at least
wxPython, Python maybe because of SWIG interface.

I spent some time on Windows, now *fundamental* parts of GUI seems to
work also under MSYS, GUI startup screen, displaying raster/vector
layers, GUI dialogs, Attribute Table Manager. Anyway there are *a lot*
problems which need to be fixed. Some screenshots

http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS#MS_Windows

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

Hamish · March 2, 2008, 6:59pm

Martin Landa wrote:

Some screenshots

http://grass.gdf-hannover.de/wiki/WxPython-based_GUI_for_GRASS#MS_Windows

Very nice! these will look great on the main "platforms" screenshots
page.

One thing I noticed:
The start screen screenshot includes "C:/grassdata" which will
instantly look very wrong to MS Windows-only users.
?
Can C:\ be used or does it need to be a forward slash?

Great use of the "grass" desktop background!

We have a GRASS icon for MS Windows in SVN, could it be used on the top
right corner of the windows and the taskbar? lib/init/grass.ico

In the GIS manager window layer list it possible to pack the [100%] box
at the right edge of the line?

Hamish

____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

Hamish · March 2, 2008, 7:03pm

ps- on:
http://grass.osgeo.org/platforms/index.php
MS Windows is a dead link:
http://grass.osgeo.org/platforms/wingrass

any ideas where that URL got to?

Hamish

____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ