Martin, Did you by chance use cmake to build geos? I built 1.9.1 against geos 3.3.5, but used cmake when building geos. It appears the output files are named differently when cmake is used. If you did use cmake, then it looks like you need to specify:
GEOS_LIB = $(GEOS_DIR)/lib/geos_c.lib if normal nmake was used without cmake generated files then it appears geos_c_i.lib is the proper lib. kss On Wed, Sep 5, 2012 at 2:04 PM, Martin Chapman <chapm...@pixia.com> wrote: > I love this user group. Thanks Joaquim! > > > > Best regards, > > Martin > > > > > > *From:* Joaquim Luis [mailto:jl...@ualg.pt] > *Sent:* Wednesday, September 05, 2012 2:03 PM > *To:* Martin Chapman > *Cc:* gdal-dev@lists.osgeo.org > > *Subject:* Re: [gdal-dev] GEOS Ver 3.3.5 and GDAL Ver 1.91 > > > > On 05-09-2012 20:33, Martin Chapman wrote: > > All, > > > > I am trying to compile GDAL 1.91 with GEOS version 3.3.5 on windows 7 x64 > and the nmake.opt file does not seem to match the directory structure of > the latest GEOS. Am I missing something simple? Any help is much > appreciated. > > > > Muchos gracias, > > > > Martin > > > > > Martin, > > I have built GDAL trunk recently with GEOS 3.3.5 with no problems, but I > use a name coding for the dir where the libs are stored. > For example, for GEOS I have in my nmake.local > > GEOS_DIR = C:\programs\compa_libs\geos-3.3.5\compileds > GEOS_CFLAGS = -I$(GEOS_DIR)/$(LIB_CC)/include -DHAVE_GEOS > GEOS_LIB = $(GEOS_DIR)/$(LIB_CC)/lib/geos_c_i.lib > > where $(LIB_CC) translates to > VC10_64 or VC10_32 > depending whether I'm building 32 or 64 bits versions > Off course, when I compiled GEOS, I stored the libs in > $(GEOS_DIR)/$(LIB_CC)/lib and the headers in $(GEOS_DIR)/$(LIB_CC)/include > > Joaquim > > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev >
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
