I’d like to create a
-sys crate for
libspatialindex. Ideally, I’d like to provide targets for *nix, macOS, and Windows. The library has a
cmake-style build process, and it doesn’t have any exotic dependencies, as far as I can tell. I can build it locally, generate bindings using
bindgen, and my tests are passing, so it certainly works at a basic level. Some questions:
- Are there some clear examples of cross-platform
build.rsscripts for libraries that use
- What do I do in cases where the library already exists on the system? I’d prefer to be conservative here and not even check for it, always using the version built from source. Is this OK?
- Is there a convention for an install location; is it OK to keep the built library within the crate, as opposed to putting it in e.g.
- The crates.io documentation says sys crates should not provide bindings, only declarations. Is it OK to autogenerate these using e.g.