Remove bluetooth_flatbuffer_tests from TEST_MAPPING

This module doesn't exist anymore but the entry still did.
This CL simply removed the invalid TEST_MAPPING entry

Test: presubmit
Bug: 401287460
Change-Id: Ibaff02a8424576196284df191767a87142dc626b
1 file changed
tree: 6fd271d5e6cc1cbe315188c728e1ee33eddfb7c5
  1. .bazelci/
  2. .github/
  3. android/
  4. bazel/
  5. benchmarks/
  6. CMake/
  7. conan/
  8. dart/
  9. docs/
  10. docs-old/
  11. examples/
  12. go/
  13. goldens/
  14. grpc/
  15. include/
  16. java/
  17. js/
  18. kotlin/
  19. lobster/
  20. lua/
  21. mjs/
  22. net/
  23. nim/
  24. php/
  25. python/
  26. reflection/
  27. rust/
  28. samples/
  29. scripts/
  30. snap/
  31. src/
  32. swift/
  33. tests/
  34. ts/
  35. .bazelignore
  36. .bazelrc
  37. .clang-format
  38. .clang-tidy
  39. .editorconfig
  40. .eslintrc.js
  41. .gitattributes
  42. .gitignore
  43. .npmrc
  44. Android.bp
  45. BUILD.bazel
  46. build_defs.bzl
  47. CHANGELOG.md
  48. CMakeLists.txt
  49. composer.json
  50. conanfile.py
  51. CONTRIBUTING.md
  52. extensions.bzl
  53. FlatBuffers.podspec
  54. Formatters.md
  55. LICENSE
  56. METADATA
  57. MODULE.bazel
  58. MODULE_LICENSE_APACHE2
  59. OWNERS
  60. package.json
  61. Package.swift
  62. pnpm-lock.yaml
  63. README.android
  64. README.md
  65. SECURITY.md
  66. swift.swiftformat
  67. TEST_MAPPING
  68. tsconfig.json
  69. tsconfig.mjs.json
  70. typescript.bzl
README.md

logo FlatBuffers

Build status BuildKite status Fuzzing Status Discord Chat Twitter Follow Twitter Follow

FlatBuffers is a cross platform serialization library architected for maximum memory efficiency. It allows you to directly access serialized data without parsing/unpacking it first, while still having great forwards/backwards compatibility.

Quick Start

  1. Build the compiler for flatbuffers (flatc)

    Use cmake to create the build files for your platform and then perform the compilation (Linux example).

    cmake -G "Unix Makefiles"
    make -j
    
  2. Define your flatbuffer schema (.fbs)

    Write the schema to define the data you want to serialize. See monster.fbs for an example.

  3. Generate code for your language(s)

    Use the flatc compiler to take your schema and generate language-specific code:

    ./flatc --cpp --rust monster.fbs
    

    Which generates monster_generated.h and monster_generated.rs files.

  4. Serialize data

    Use the generated code, as well as the FlatBufferBuilder to construct your serialized buffer. (C++ example)

  5. Transmit/store/save Buffer

    Use your serialized buffer however you want. Send it to someone, save it for later, etc...

  6. Read the data

    Use the generated accessors to read the data from the serialized buffer.

    It doesn't need to be the same language/schema version, FlatBuffers ensures the data is readable across languages and schema versions. See the Rust example reading the data written by C++.

Documentation

Go to our landing page to browse our documentation.

Supported operating systems

  • Windows
  • macOS
  • Linux
  • Android
  • And any others with a recent C++ compiler (C++ 11 and newer)

Supported programming languages

Code generation and runtime libraries for many popular languages.

  1. C
  2. C++ - snapcraft.io
  3. C# - nuget.org
  4. Dart - pub.dev
  5. Go - go.dev
  6. Java - Maven
  7. JavaScript - NPM
  8. Kotlin
  9. Lobster
  10. Lua
  11. PHP
  12. Python - PyPI
  13. Rust - crates.io
  14. Swift - swiftpackageindex
  15. TypeScript - NPM
  16. Nim

Versioning

FlatBuffers does not follow traditional SemVer versioning (see rationale) but rather uses a format of the date of the release.

Contribution

To contribute to this project, see CONTRIBUTING.

Community

Security

Please see our Security Policy for reporting vulnerabilities.

Licensing

Flatbuffers is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.