Changes between Version 13 and Version 14 of RFC6

Timestamp:

Oct 3, 2017, 8:14:42 AM (7 years ago)

Author:

robe

Comment:

--

RFC6

@@ -29 +29 @@
 
 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
+Also the C++ headers will not installed.
+
+If users choose to build with the cplusplus-sdk, a warning will be shown before start of compile stating:
+
+
+{{{
+The GEOS project does not guarantee ABI stability of the C++ API during minor updates. This means your code may need recompilation or changes to upgrade to next minor version of GEOS.  If you want ABI stability from minor version to minor version, you should use the C-API instead.
+}}}
+
  
 As proposed in [https://lists.osgeo.org/pipermail/geos-devel/2017-October/008071.html]
@@ -43 +51 @@
 
 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 ...)