Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
meos-sys
Low level MEOS C API bindings for MEOS.
It provides C-interface as is. If you want to use a more Rust-friendly crate, use the meos crate.
You can also find it on crates.io.
Versions >= 1.1 are supported.
Usage
You need to select as features what version do you want to obtain the bindings from (v1_1, v1_2), or alternatively, whether you want to build MEOS from scratch (bundled). This will mean adding to your Cargo.toml:
# Cargo.toml
[]
= { = "0.1.8", = ["v1_2"] }
Build
The build by default will use system-installed MEOS, pkg-config is used to automatically detect MEOS
If MEOS is in a custom location, you can instead use the MEOS_LIB_DIR environment variable to
configure MEOS detection.
If MEOS_LIB_DIR is not also in your system's standard dynamic library search
path, you may need to add it to the dynamic library search path before
running the tests or executable produced by cargo build.
Linux:
LD_LIBRARY_PATH=<path
MacOS:
DYLD_FALLBACK_LIBRARY_PATH=<path
You can also enable the bundled feature to build MEOS from scratch. Note you will still have to have installed in your system GEOS, PROJ and JSON-C libraries. You can install all of them by running the following command in your (Debian based) machine:
Binding generation
The 1.2 and 1.1 versions are already available as prebuilt bindings. Alternatively, you can generate your own bindings from your libmeos installation by specifying the bindgen feature.