darion-yaphet commented on code in PR #3559:
URL: https://github.com/apache/brpc/pull/3559#discussion_r4280530301


##########
example/benchmark_fb/README.md:
##########
@@ -0,0 +1,254 @@
+# FlatBuffers RPC example
+
+[English enablement guide](../../docs/en/flatbuffers.md) |
+[中文启用与验证指南](../../docs/cn/flatbuffers.md)
+
+This directory contains independent client and server programs using the
+`fb_rpc` protocol, generated FlatBuffers services, and
+`brpc::flatbuffers::Message`. The directory name is retained for continuity;
+this is a **bounded functional example**, not a performance comparison.
+
+The schema declares `BenchmarkService.Echo` with stable wire method ID **7**.
+The generated stub calls `Channel::FBCallMethod`; the server registers the
+generated service with `Server::AddFlatBuffersService`.
+
+## Prerequisites
+
+Use an existing local C++ toolchain and matching development installations of
+Protobuf, gflags, leveldb, OpenSSL, zlib, and FlatBuffers. The runtime is not
+Protobuf-free: its controller/closure interfaces and other bRPC components 
still
+need Protobuf. The projects require CMake 3.16 or newer; the CTest commands 
below
+use CMake/CTest 3.17+ for `--no-tests=error`. With 3.16, run `smoke.py` 
directly.
+Use a single-configuration generator (Unix Makefiles or Ninja) and Python 3 for
+the smoke test. The commands below target
+Linux and macOS and do not download dependencies.
+
+The runtime needs FlatBuffers headers, but building `brpc_flatc` also needs the
+official `libflatbuffers`. The official `flatc` generates table types; it 
cannot
+replace `brpc_flatc`, which generates bRPC services. The repository's ON gate 
pins
+FlatBuffers 25.2.10; use a matching complete installation to reproduce that 
gate.

Review Comment:
   It has been precisely set to 25.2.10, so the distribution software packages 
(Ubuntu provides 23.5.26) and the updated versions of Homebrew cannot be used. 
Could you please record how this version number was adjusted, or accept a 
tested range? This can be considered as a follow-up matter.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to