On 03/04/07 20:49, Michael Barton wrote:
Moritz,
This site has been unavailable since I got your message last night. Perhaps
because of undue popularity??
No, the problem was that I had left on vacation, but we had a power cut at the office, so my machine was left shut off.
Now it is available again.
I would really appreciate someone testing these and tell me whether I did things correctly and they work...
Two things I probably need to add:
- We do need a shell for some commands, so I think that at this stage msys is a requirement. (Paul ?)
- I can provide the database drivers (postgres, sqlite) if someone tells me how to compile them separately. Do I have to rerun configure and then make in the individual directories ?
Moritz
Hello Moritz
On Tue, 10 Apr 2007, Moritz Lennert wrote:
On 03/04/07 20:49, Michael Barton wrote:
Moritz,
This site has been unavailable since I got your message last night. Perhaps
because of undue popularity??
No, the problem was that I had left on vacation, but we had a power cut at the office, so my machine was left shut off.
Now it is available again.
I would really appreciate someone testing these and tell me whether I did things correctly and they work...
Sorry still have not had time yet...
Two things I probably need to add:
- We do need a shell for some commands, so I think that at this stage msys is a requirement. (Paul ?)
Yes, although there is a *lot* you can do without using shell scripts, and a shell is not needed for any of the GRASS start-up or module-running infrastructure any more, only for modules that actually are shell scripts. Also we need to investigate the possibility of using non-Msys shells (e.g. the one that comes with Windows services for Unix???) and the fact that Msys still needs the path set to find its utilities and things like that. A way to go on this one.
P.S. attached are a couple of patches to the current CVS to fix compilation of libraster and r.mapcalc on Windows. I don't have convenient CVS access right now to apply them...
Paul
(attachments)
diff.txt (1.11 KB)
Moritz Lennert wrote:
- I can provide the database drivers (postgres, sqlite) if someone tells
me how to compile them separately. Do I have to rerun configure and then
make in the individual directories ?
Yes.
For future builds, you can enable whichever database options are
supported on the build system. There is no longer any reason to
disable the database options when building GRASS (at one time,
using --with-postgres resulted in an NVIZ binary which wouldn't run
without it, but that's no longer the case).
However, if you're using a shared GDAL library, you might want to
manually edit the GDALLIBS definition in Platform.make to remove its
dependencies, as those will be propagated to any executables which use
it.
[If you aren't using a shared GDAL library, or if you're including the
GDAL library in the GRASS package, you'll need to give some
consideration as to which formats are supported.]
--
Glynn Clements <glynn@gclements.plus.com>
Paul Kelly wrote:
P.S. attached are a couple of patches to the current CVS to fix
compilation of libraster and r.mapcalc on Windows. I don't have convenient
CVS access right now to apply them...
Committed.
--
Glynn Clements <glynn@gclements.plus.com>