The problem is not that geos_c.h is missing, it's that the vdigit
makefile needs the geos include path in its EXTRA_CFLAGS.
The vlib compile does include this, as a part of VECT_CFLAGS, thus
it's not failing.
On Mar 31, 2009, at 12:02 AM, Martin Landa wrote:
Hi,
2009/3/31 Michael Barton
OK.
William, how to test?
Michael
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University
Phone: 480-965-6262
Fax: 480-965-7671
www:
On Mar 30, 2
I will put checking for geos_c.h to configure. M.
2009/3/31 Martin Landa :
> Hi,
>
> 2009/3/31 Michael Barton :
>> So you're saying that vdigit doesn't work again because of the geos problem?
>
> again, problem? ;-)
>
> I wasn't expecting that if you have GEOS installed that geos_c.h is
> not avai
Hi,
2009/3/31 Michael Barton :
> So you're saying that vdigit doesn't work again because of the geos problem?
again, problem? ;-)
I wasn't expecting that if you have GEOS installed that geos_c.h is
not available. If so than vector libs compilation fail. In this case
checking for geos-config is n
On Mar 30, 2009, at 7:27 PM, William Kyngesburye wrote:
Finally got some time to actually try it. Error in python vdigit -
it's looking for geos_c.h, from Vect.h.
For the linking, it works on OSX as is, but only because I include
both C++ and C APIs (libgeos and libgeos_c) in the same bi
Finally got some time to actually try it. Error in python vdigit -
it's looking for geos_c.h, from Vect.h.
For the linking, it works on OSX as is, but only because I include
both C++ and C APIs (libgeos and libgeos_c) in the same binary in the
GEOS framework. On other platforms, libgeos_c
On Mar 30, 2009, at 4:57 PM, Martin Landa wrote:
Is GEOS support really using the C++ API? geos-config --libs only
returns
the C++ linking info.
No, C API.
Then add -lgeos_c the GEOS_LIBS? Though you might want an extra check
to verify libgeos_c exists.
Maybe this is where Michael is
Hi,
2009/3/30 William Kyngesburye :
> I looked at configure to see what it's doing for GEOS. Looks like the
> geos-config option should be the one. config.log is your friend when
> configure fails.
see ./configure --help
--with-geos takes path to geos-config similary to --with-gdal.
> Is GEOS
I looked at configure to see what it's doing for GEOS. Looks like the
geos-config option should be the one. config.log is your friend when
configure fails.
Is GEOS support really using the C++ API? geos-config --libs only
returns the C++ linking info.
Searching the rest of the source,
2009/3/30 Michael Barton :
> This doesn't work either, nor does --without-geos.
--with-geos=no
> There seems to be something broken here.
Update your local copy, from r36538 is default "--with-geos=no".
M.
--
Martin Landa * http://gama.fsv.cvut.cz/~landa
_
Hi,
2009/3/30 Michael Barton :
> Neither one of these work, even though they correctly map to the location of
> geos-config and the lib and include directories (set up from your frameworks
> packages). I'll try to compile without GEOS, though I don't know what I'll
> be missing there.
I changed d
On Mar 30, 2009, at 11:38 AM, Martin Landa wrote:
Hi,
2009/3/30 Michael Barton :
I just did an svn update from trunk and tried to configure GRASS 7
prior to
compiling. I'm using the same configure string that worked
successfully 48
hours ago. But configure failed with an geos-config erro
On Mar 30, 2009, at 12:00 PM, William Kyngesburye wrote:
Ah. I guess you could do similar to how the other frameworks are
handled:
--with-geos-includes=/Library/Frameworks/GEOS.framework/unix/include
--with-geos-libs=/Library/Frameworks/GEOS.framework/unix/lib
-OR-
--with-geos=/Librar
Ah. I guess you could do similar to how the other frameworks are
handled:
--with-geos-includes=/Library/Frameworks/GEOS.framework/unix/include --
with-geos-libs=/Library/Frameworks/GEOS.framework/unix/lib
-OR-
--with-geos=/Library/Frameworks/GEOS.framework/Programs/geos-config
depending o
Hi,
2009/3/30 Markus Neteler :
> On Mon, Mar 30, 2009 at 8:38 PM, Martin Landa wrote:
>> Hi,
>>
>> 2009/3/30 Michael Barton :
>>> I just did an svn update from trunk and tried to configure GRASS 7 prior to
>>> compiling. I'm using the same configure string that worked successfully 48
>>> hours ag
On Mon, Mar 30, 2009 at 8:38 PM, Martin Landa wrote:
> Hi,
>
> 2009/3/30 Michael Barton :
>> I just did an svn update from trunk and tried to configure GRASS 7 prior to
>> compiling. I'm using the same configure string that worked successfully 48
>> hours ago. But configure failed with an geos-con
Hi,
2009/3/30 Michael Barton :
> I just did an svn update from trunk and tried to configure GRASS 7 prior to
> compiling. I'm using the same configure string that worked successfully 48
> hours ago. But configure failed with an geos-config error (below). Is this a
> bug, or do I need to change my
Look in config.log to see why.
On Mar 30, 2009, at 12:56 PM, Michael Barton wrote:
I just did an svn update from trunk and tried to configure GRASS 7
prior to compiling. I'm using the same configure string that worked
successfully 48 hours ago. But configure failed with an geos-config
erro
I just did an svn update from trunk and tried to configure GRASS 7
prior to compiling. I'm using the same configure string that worked
successfully 48 hours ago. But configure failed with an geos-config
error (below). Is this a bug, or do I need to change my config string
to something diffe
19 matches
Mail list logo
