Glynn Clements wrote: > Benjamin Ducke wrote: > >>> 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 >>> MSys/MinGW? >> 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. > > I'm talking about cases where the executable needs to open files in > /etc, /usr/lib, /usr/share, etc. I'm guessing that the executable > isn't going to be expecting "/" to be wherever you put GRASS. >
Do you have specific examples that I could test? -- 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@grass.itc.it http://grass.itc.it/mailman/listinfo/grass-dev
