[GRASS-dev] Wingrass and TclTk
benjamin.ducke at ufg.uni-kiel.de
Wed Oct 31 09:43:51 EDT 2007
Glynn Clements wrote:
> Benjamin Ducke wrote:
>>> The relative path will only work if grass63.bat is installed in
>>> c:\msys\1.0, so there's no benefit to using it.
>> Not quite. With the setup above, GRASS can be installed _anywhere_ on
>> the file system. The only prerequisite is that grass63.bat sits
>> in the same folder as the GRASS install dir.
>> E.g. on my harddisk I have grass63.bat in c:\WinGRASS\
>> and the GRASS dir (grass-6.3.cvs) in the same folder.
>> I then copied C:\msys\1.0\bin, dll and share
>> (at least the parts that I needed for using the shell) into
>> This way, I have a completely self-contained GRASS distribution.
>> I can add more bits an pieces (such as R) easily as needed and
>> at the end, put everything into on ZIP for distribution.
> Have you tested this on a system which doesn't already have MSys
I'll do that in a moment and tell you about the results.
> The scripts use a lot of common Unix utilities; have you included
> those? If they need to read any data files, are they looking for them
> in the WinGRASS directory or in the already-installed version of
Yes, I made a complete install of MSYS + tools and just copied
everything over. I was going to look through it later to check
what can be thrown out and bit by bit make a list of what needs
to go in.
The wingrass.bat script I posted early starts up cmd.exe in the user's
Windows home directory. Sh.exe also respects that. Thus, scripts look
for files in the user home dir first.
Which I think is OK.
Benjamin Ducke, M.A.
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
D 24098 Kiel
Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
More information about the grass-dev