[EMAIL PROTECTED] wrote:
On Wed, Nov 15, 2006 at 09:20:57AM -0800, Paul Ramsey wrote:
On 15-Nov-06, at 9:59 AM, Frank Warmerdam wrote:
It does still really suck that I have to configure geos on unix
just to
get a geos_c.h.vc (which I copied from the geos_c.h produced on unix).
Hopefully the rules for producing the packaged source tarballs (as
opposed
to pulling from SVN) will produce geos_c.h.vc for distribution?
If you pull geos-svn.tar.gz, the snapshot source, you'll find that it
has been auto-generated.
The ./configure scripts generates from geos_c.h.vc.in, which is
out of sync, unless I'm missing something.
So, do we drop the whole .vc thing, because it is out of date and
unmaintained? Or do we maintain it up to a level of utility? Do we
revert the .in generation (all it gains us is automatic
synchronization with the version information from the top of the tree)?
I suggest we only generate geos_c.h, but also distribute it.
Trying this now..
Strk,
Dropping the geos_c.h.vc entirely would be fine if distributed source
files include geos_c.h, but then we will need to remove the rule for
copying geos_c.h.vc to geos_c.h from the source/Makefile.vc.
I'd be wiling to try a fixed up source distribution if you guys like.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, [EMAIL PROTECTED]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
_______________________________________________
geos-devel mailing list
geos-devel@geos.refractions.net
http://geos.refractions.net/mailman/listinfo/geos-devel
