[geos-devel] Include Refactoring

[Martin Davis]

I agree with Norman - it seems much cleaner to put all the include files into a geos subdirectory.

Actually, I'm surprised that this concept of installing include files into a single common directory even exists.  Surely the directory gets ridiculouly massive, and there's huge risk of name collisions?  Why wouldn't all the src files for GEOS go into single geos subdirectory (e.g. the way it's organized on the CVS?)

The current way just seems like a Unix version of "DLL hell"....

Martin Davis, Senior Technical Specialist
Vivid Solutions Inc.
Suite #1A-2328 Government Street   Victoria, B.C.   V8T 5G5
Phone: (250) 385 6040    Fax: (250) 385 6046
EMail: mbdavis at vividsolutions.com  Web: www.vividsolutions.com


> -----Original Message-----
> From: Norman Vine [mailto:nhv at cape.com]
> Sent: Wednesday, February 12, 2003 9:53 AM
> To: GEOS Development List
> Subject: RE: [geos-devel] Include Refactoring
> 
> 
> Paul Ramsey writes:
> > 
> > The headers needed by external programs in order to call 
> geos objects 
> > and know what functions are inside the library. The headers which a 
> > 'make install' would place in the system include directory 
> for use by 
> > other software.  Right now, 'make install' on geos installs the 
> > following in /usr/local/include:
> 
> Instead of prepending 'geos_',  I suggest installing the headers
> into a 'geos' subdirectory
> 
> ie normally install into /usr/local/include/geos 
> or /usr/local/include/libgeos
> 
> Cheers
> 
> Norman
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel
>