Changes between Version 22 and Version 23 of RFC6

Timestamp:

Oct 4, 2017, 7:24:42 AM (7 years ago)

Author:

robe

Comment:

--

RFC6

@@ -76 +76 @@
 1) Package Distributions do not need compile with these flags, though they may choose to at their own risk to support C++ API users.
 
-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
+2) The end effect being, no C++ headers installed  and just the C header file installed.
 
-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.
+3) People building their own binaries or their own projects that utilize the C++ API may not be able to build using a packaged libgeosdev-++ if packagers don't compile with c++ support.
+Those who do use dev packages, will get the above warning when they compile.
 
 That way new projects will be clear about what compromise they are making using the C++ API.