/usr/share/doc/librttopo-dev/README.md is in librttopo-dev 1.0.0-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 | RT Topology Library
===================
## Build status
[![Gitlab-CI](https://gitlab.com/rttopo/rttopo/badges/master/build.svg)]
(https://gitlab.com/rttopo/rttopo/commits/master)
## About
The RT Topology Library exposes an API to create and manage standard
(ISO 13249 aka SQL/MM) topologies using user-provided [data stores]
(doc/DATASTORES.md) and released under the GNU GPL license
(version 2 or later).
The code is derived from [PostGIS](http://postgis.net) liblwgeom
library enhanced to provide thread-safety, have less dependencies
and be independent from PostGIS release cycles.
The RT Topology Library was funded by "Regione Toscana - SITA"
(CIG: 6445512CC1), which also funded many improvements in the
originating liblwgeom.
Official code repository is https://git.osgeo.org/gogs/rttopo/librttopo.
A mirror exists at https://gitlab.com/rttopo/rttopo, automatically
updated on every push to the official repository.
Development mailing list:
https://lists.osgeo.org/mailman/listinfo/librttopo-dev
## Building, testing, installing
### Unix
Using Autotools:
./autogen.sh # in ${srcdir}, if obtained from GIT
${srcdir}/configure # in build dir
make # build
make check # test
make install # or install-strip
### Microsoft Windows
See [separate document](doc/BUILDING-ON-WINDOWS.md)
## Using
The public header for topology support is `librttopo.h`.
The caller has to setup a backend interface (`RTT_BE_IFACE`) implementing
all the required callbacks and will then be able to use the provided
editing functions.
The contract for each callback is fully specified in the header.
The callbacks are as simple as possible while still allowing for
backend-specific optimizations.
The backend interface is an opaque object and callabcks are registered
into it using free functions. This is to allow for modifying the required
set of callbacks between versions of the library without breaking backward
compatibility.
|