README
1Standalone GRASS Drivers for GDAL and OGR
2=========================================
3
4This package contains standalone drivers for GRASS raster and vector
5files that can be built after GDAL has been built and installed as an
6"autoload" driver.
7
8This is particularly useful in resolving problems with GRASS depending
9on GDAL, but GDAL with GRASS support depending on GRASS. With this
10package you can configure and install GDAL normally (--without-grass), then
11build and install GRASS normally and finally build and install this driver.
12
13To build this driver it is necessary for it to find GDAL and GRASS support
14files. Typically the configure and build process would look something like:
15
16./configure --with-gdal=/usr/local/bin/gdal-config --with-grass=/usr/local/grass-7.0.1
17make
18sudo make install
19
20See also:
21
22 https://gdal.org/
23 https://grass.osgeo.org
24
25
26---
27
28FAQs
29----
30
31
32Question:
33
34I am trying to install gdal-grass 3.1.3 on RedHat Enterprise Linux
35advanced server 3.0. I have previously installed gdal 3.1.3 --without-grass,
36and GRASS 7.0.1 with GDAL. I have tried to configure gdal-grass
37with:
38
39./configure --with-gdal=/usr/local/bin/gdal-config \
40 --with-grass=/usr/local/grass-7.0.1
41
42It seems to find gdal alright, but then balks at the Grass location. The
43Grass location specified above is indeed the correct location. I have
44also tried adding --with-grass=/usr/local/grass-7.0.1/lib, but with no
45success. My error is:
46
47...
48checking for G_asprintf in -lgrass_gis ... no
49configure: error: --with-grass=/usr/local/grass-7.0.1 requested, but
50libraries not found?
51
52
53Answer:
54
55Your problem is likely to be solved by editing /etc/ld.so.conf to
56include the locations of proj, gdal, grass, and geos. Specifically,
57the full path to both gdal-config and geos-config, and the full paths
58to the library locations of proj (often /usr/local/lib) and grass
59(/usr/local/grass-7.0.1/lib). After editing ld.so.conf, run ldconfig,
60and you should be good to go.
61
62I ran into this problem this weekend (and posted for help to this
63list), so it seems to be a pretty common issue.
64