4 releases

0.8.2 Jul 24, 2023
0.8.1 Jun 9, 2023
0.8.0 Apr 19, 2022
0.7.0 Sep 27, 2021

#188 in Geospatial

Download history 12/week @ 2023-12-29 25/week @ 2024-01-05 21/week @ 2024-01-12 13/week @ 2024-01-19 16/week @ 2024-01-26 14/week @ 2024-02-09 18/week @ 2024-02-16 17/week @ 2024-02-23 17/week @ 2024-03-01 27/week @ 2024-03-08 31/week @ 2024-03-15 29/week @ 2024-03-22 42/week @ 2024-03-29 10/week @ 2024-04-05

85 downloads per month
Used in 3 crates (via swiftnav)

LGPL-3.0

15MB
30K SLoC

C 25K SLoC // 0.2% comments Bitbake 2.5K SLoC // 0.5% comments M4 1K SLoC // 0.4% comments Python 597 SLoC // 0.3% comments Shell 357 SLoC // 0.1% comments Automake 304 SLoC // 0.1% comments C++ 277 SLoC // 0.1% comments Bazel 178 SLoC // 0.0% comments Rust 175 SLoC // 0.1% comments XSL 99 SLoC // 0.1% comments Perl 91 SLoC // 0.2% comments TypeScript 41 SLoC // 0.0% comments

Contains (obscure autoconf code, 15KB) configure.ac, (obscure autoconf code, 1KB) configure.ac

swiftnav

swiftnav is a crate that implements GNSS utility functions for use by software-defined GNSS receivers or software requiring GNSS functionality. It is intended to be as portable as possible and has limited dependencies.

swiftnav does not provide any functionality for communicating with Swift Navigation receivers. See libsbp to communicate with receivers using Swift Binary Protocol (SBP).

swiftnav-sys

swiftnav-sys is a crate which builds and exposes Rust FFI bindings for the libswiftnav C library.

Publishing a new release

Releases are done against the master branch. Use the cargo publish tool. First release the swiftnav-sys crate:

Update the swiftnav-sys crate version:

cd swiftnav-sys
sed -i 's@version = "0.8.1"@version = "0.8.2"@' Cargo.toml

Then release the package:

cd swiftnav-sys
cargo publish

Update the swiftnav crate version:

cd swiftnav
sed -i 's@version = "0.8.1"@version = "0.8.2"@' Cargo.toml

Then release the swiftnav crate:

cd swiftnav
cargo publish

License

This crate is distributed under the terms of the LGPLv3, full details are available in the LICENSE file.

No runtime deps