Changes between Version 12 and Version 13 of RFC6
- Timestamp:
- Oct 3, 2017, 8:10:47 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RFC6
v12 v13 1 = GEOS RFC 6: Require explicit configure to use the C++ API and ship c++ headers=1 = GEOS RFC 6: Require explicit configure to use the C++ API = 2 2 3 ||RFC 6: ||Discourage use of C++ API requiring a configure switch to install the c++ headers||3 ||RFC 6: ||Discourage use of C++ API by requiring a configure switch to install the c++ headers and SDK|| 4 4 ||Author: ||Regina Obe || 5 5 ||Contact:||lr@pcorp.us || … … 20 20 {{{ 21 21 #autoconf users 22 ./configure --enable-c++-headers-install22 ./configure --with-cplusplus-sdk-install 23 23 24 24 #cmake users 25 cmake -DINCLUDE_CPP_HEADERS=1 25 cmake -DINSTALL_CPLUSPLUS_SDK 26 26 27 27 }}} 28 28 29 30 If cplusplus sdk install is not expressly requested only the C library (not linked just a single library will be created). 31 Also the C++ headers will not installed 29 32 30 As proposed in [https://lists.osgeo.org/pipermail/geos-devel/2017-October/0080 54.html]33 As proposed in [https://lists.osgeo.org/pipermail/geos-devel/2017-October/008071.html] 31 34 32 35 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. 38 41 42 So the purpose of the above is to affect the following change: 43 44 1) Package Distributions willnot compile with these flags 45 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 46 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. 47 They will have to compile their own GEOS. 48 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. 49 50 That way new projects will be clear about what compromise they are making using the C++ API. 51 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 ...) 39 52 40 53 54 55