[geos-devel] Include Refactoring

[Paul Ramsey]

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:

-rw-r--r--    1 root     root        26474 Feb 12 09:22 geom.h
-rw-r--r--    1 root     root         6912 Feb 12 09:22 geosAlgorithm.h
-rw-r--r--    1 root     root        17260 Feb 12 09:22 graph.h
-rw-r--r--    1 root     root         4987 Feb 12 09:22 graphindex.h
-rw-r--r--    1 root     root         4301 Feb 12 09:22 io.h
-rw-r--r--    1 root     root         1630 Feb 12 09:22 operation.h
-rw-r--r--    1 root     root         3624 Feb 12 09:22 opRelate.h
-rw-r--r--    1 root     root          229 Feb 12 09:22 platform.h
-rw-r--r--    1 root     root          936 Feb 12 09:22 util.h

It also installs the libraries in /usr/local/lib

-rw-r--r--    1 root     root     15002262 Feb 12 09:22 libgeos.a
-rwxr-xr-x    1 root     root          705 Feb 12 09:22 libgeos.la*
lrwxrwxrwx    1 root     root           16 Feb 12 09:22 libgeos.so -> 
libgeos.so.1.0.0*
lrwxrwxrwx    1 root     root           16 Feb 12 09:22 libgeos.so.1 -> 
libgeos.so.1.0.0*
-rwxr-xr-x    1 root     root      3624493 Feb 12 09:22 libgeos.so.1.0.0*



Martin Davis wrote:
> Paul, can you give an example of what you mean?  It's not clear what you mean by "API headers".
> 
> 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: Paul Ramsey [mailto:pramsey at refractions.net]
>>Sent: Wednesday, February 12, 2003 9:25 AM
>>To: GEOS Development List
>>Subject: [geos-devel] Include Refactoring
>>
>>
>>
>>For the API headers, it would probably be wise to do a mass 
>>renaming, so 
>>that all the headers which get installed have a geos_ prefix. 
>>That way 
>>we can lower our odds of name collision on systems we install on. 
>>(Martin, insert comment about beauty of Java packaging here. :)
>>
>>I was just looking at what is required to do an alpha release of geos 
>>(to go alongside a pre-release of geos-enabled postgis) and having 
>>nicely named includes would be good.
>>
>>Thoughts?
>>
>>P.
>>
>>-- 
>>       __
>>      /
>>      | Paul Ramsey
>>      | Refractions Research
>>      | Email: pramsey at refractions.net
>>      | Phone: (250) 885-0632
>>      \_
>>
>>
>>_______________________________________________
>>geos-devel mailing list
>>geos-devel at geos.refractions.net
>>http://geos.refractions.net/mailman/listinfo/geos-devel
>>
> 
> 
> _______________________________________________
> geos-devel mailing list
> geos-devel at geos.refractions.net
> http://geos.refractions.net/mailman/listinfo/geos-devel


-- 
       __
      /
      | Paul Ramsey
      | Refractions Research
      | Email: pramsey at refractions.net
      | Phone: (250) 885-0632
      \_