Changes between Version 12 and Version 13 of RFC6

Timestamp:

Oct 3, 2017, 8:10:47 AM (7 years ago)

Author:

robe

Comment:

--

RFC6

@@ -1 @@
-= GEOS RFC 6: Require explicit configure to use the C++ API and ship c++ headers =
+= GEOS RFC 6: Require explicit configure to use the C++ API =
 
-||RFC 6:  ||Discourage use of C++ API requiring a configure switch to install the c++ headers||
+||RFC 6:  ||Discourage use of C++ API by requiring a configure switch to install the c++ headers and SDK||
 ||Author: ||Regina Obe        ||
 ||Contact:||lr@pcorp.us    ||
@@ -20 +20 @@
 {{{
 #autoconf users
-./configure --enable-c++-headers-install
+   ./configure --with-cplusplus-sdk-install
 
 #cmake users
-cmake -DINCLUDE_CPP_HEADERS=1
+   cmake -DINSTALL_CPLUSPLUS_SDK
 
 }}}
 
+
+If cplusplus sdk install is not expressly requested only the C library (not linked just a single library will be created).
+Also the C++ headers will not installed
  
-As proposed in [https://lists.osgeo.org/pipermail/geos-devel/2017-October/008054.html]
+As proposed in [https://lists.osgeo.org/pipermail/geos-devel/2017-October/008071.html]
 
 I propose doing this in GEOS 3.7.0.
@@ -37 +40 @@
 Currently [https://github.com/openstreetmap/osm2pgsql/issues/634 osm2pgsql (which is switching away from GEOS and using Osmium instead)] (and before Osmium, which switched from using GEOS and now uses GDAL) and OSSIM are the only ones that used the GEOS C++ API and largely distributed in shared environment.  We want to discourage future projects that plan to be used in a shared environment from using the GEOS C++ API and to stick with the GEOS C API.
 
+So the purpose of the above is to affect the following change:
+
+1) Package Distributions willnot compile with these flags
+2) The end effect being, no C++ header, no C++ library to worry about -- just a single .so or .dll  and a C header file
+3) People building their own binaries or their own projects that utilize the C++ API will not be able to use GEOS from packages since GEOS packages will not have the C++ API bindings they need. 
+ They will have to compile their own GEOS.
+This means if they want their product to be shipped with other distributed software and share the same GEOS, they will need to use the C-API.
+
+That way new projects will be clear about what compromise they are making using the C++ API.  
+That means they will not be able to use GEOS from packages in their CI integration (e.g. travis, appveyor etc that people commonly do apt-get ...)
 
 
+
+