flatc-fork 0.5.0+25.12.19

Vendored executable of flatbuffer's `flatc` (maintained fork).
Documentation
1
2
3
4
5
6
7
8
9
10
11
12
13
# flatc

[![crates.io](https://img.shields.io/crates/v/flatc-fork.svg)](https://crates.io/crates/flatc-fork) [![docs.rs](https://docs.rs/flatc-fork/badge.svg)](https://docs.rs/flatc-fork) [![github actions](https://github.com/itpetey/flatc.rs/workflows/ci/badge.svg)](https://github.com/itpetey/flatc.rs/actions) [![license](https://img.shields.io/badge/license-MIT-blue.svg)](./LICENSE)

**This is a fork of [github.com/chippers/flatc.rs]() that I am maintaining. All credit to @chippers for the original codebase.**

Builds [flatbuffers](https://github.com/google/flatbuffers) and provides the path to the built `flatc`. Intended for use by build scripts, but can be useful otherwise if the project is using `flatc` during runtime.

The flatbuffers version is determined by the build identifier for the crate version. `v0.2.0+2.0.0` means the crate is version `0.2.0` and the vendored flatbuffers version is `2.0.0`. There's no pressure in releasing crate version `1.0.0` since this is primarily a build tool, so it will come eventually after nothing needs to be fixed/added for a while.

## Updating `flatbuffers`

Updates are done automatically via the `release` workflow, which is run each day at 12am UTC.