QGIS » QGIS Application

Hi Markus,

The file indexStrtree.h included by the WFS provider is the exactly the one from geos. If your compiler cannot find it, it is probably in an unusual place and we should fix the build system to find it. Usually, it is in /usr/include/geos and geos.h in /usr/include. The build system assumes, that indexStrtree.h is in the geos subdirectory under the directory where geos.h is located.

Hi Marco,

for the other plugins that works. There
must be something missing in wfs/Makefile.am which is present
in the other plugin Makefile.am files.
In the old bugtracker I had reported similar things for the other
plugins which were fixes (once QGIS was still in CVS).

g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../core/ -I../../gui/ -I../../ui -I/usr/local/include -DQT3_SUPPORT -I/usr/lib64/qt4/mkspecs/default -I/usr/lib64/qt4/include/Qt3Support -I/usr/lib64/qt4/include/QtCore -I/usr/lib64/qt4/include/QtDesigner -I/usr/lib64/qt4/include/QtGui -I/usr/lib64/qt4/include/QtNetwork -I/usr/lib64/qt4/include/QtOpenGL -I/usr/lib64/qt4/include/QtSql -I/usr/lib64/qt4/include/QtXml -I/usr/lib64/qt4/include -I/usr/lib64/qt4/include/QtSvg -I/usr/lib64/qt4/include/QtTest -I/usr/lib64/qt4/include/QtDesigner -D_REENTRANT -DQT_THREAD_SUPPORT -DNO_DEBUG -I/usr/local/include -I/usr/local/include/geos -g -O2 -MT libwfsprovider_la-qgswfsprovider.lo -MD -MP -MF .deps/libwfsprovider_la-qgswfsprovider.Tpo -c qgswfsprovider.cpp  -fPIC -DPIC -o .libs/libwfsprovider_la-qgswfsprovider.o
In file included from qgswfsprovider.cpp:21:
qgswfsprovider.h:25:26: indexStrtree.h: No such file or directory

configured as:
GEOS : yes (Version 2.2.1)

locate indexStrtree.h
/usr/include/geos/indexStrtree.h

I had GEOS in an unusual place but it seems to be picked from
the System wide installation (for ./autogen.sh there is no path
indication).
But I don't see /usr/include/[geos/] listed above, is that the problem?

Best,
Markus

Hi,

when I manually add -I/usr/include/geos to above
g++ line, it compiles.

Markus

Markus,

It seems to me that your build system assumes your geos is in /usr/local, but it is in /usr/lib. Does it change anything when you do ./autogen.sh --with-geos=<path_to_geos-config> ... ?
And does your geos-config point to the right location?

Best,
Marco