jarro2783/cxxopts
Protobuf
jarro2783/cxxopts | Protobuf | |
---|---|---|
15 | 174 | |
4,002 | 63,731 | |
- | 0.6% | |
6.8 | 10.0 | |
8 days ago | 1 day ago | |
C++ | C++ | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jarro2783/cxxopts
-
Command line interface library
The most feature-rich C++ CLI library is CLI11. Other popular choices include Boost.ProgramOptions, argparse, cxxopts and others.
-
Recommended Argument Parsing Library?
I've used cxxopts and can't complain. It's available on both Conan and vcpkg.
- Confusion about libraries and project structure
-
Quick question about int main(int argc, char **argv)
For streamlined command line option parsing check out a library like cxxopts or similar. There are plenty out there.
-
How do you make a command line argument of this format: ./executableName "input = inputFileName; output = outputFileName"
Have a look at cxxopts which is similar to the python getopt functions, It's header only so easy to use (just dump the header in your project). There is also boost::program_options but this requires boost which is big.
-
CLI11 is making all the other options libraries look bad, does anyone have a comparison from experience?
I use CLI11 for more complex things, https://github.com/jarro2783/cxxopts for simpler interfaces, and boost.program_options if I have to and have boost anyways as dependency.
-
Is there a macro for the output directory on msvc?
Let the user pass the path/filename as an input argument to the program. Your main() function takes arguments from the console, so you could invoke your program as .\my_program --err_log "\path\to\my_errors.log". Of course this again only works if executed from the console - you can however create a desktop shortcut that invokes your program with this argument and you can also configure your IDE to pass this argument when running your program. To make parsing input arguments easier, use a library such as cxxopts
-
Command Line Argument That Can Take Multiple Parameters
You probably want the header only library cxxopts.
-
How to create my own command using cpp?
To make parsing command line options easier I can recommend the cxxopts library.
-
Dumb question: what data structure do you use to represent a collection of config values passed in via command line arguments/
I have previously used this: https://github.com/jarro2783/cxxopts
Protobuf
-
Hitting every branch on the way down
It's because they changed the versioning format: https://github.com/protocolbuffers/protobuf/releases?page=5
But I suppose old version still receive bugfixes.
-
Reverse Engineering Protobuf Definitions from Compiled Binaries
For at least 4 years protobuf has had decent support for self-describing messages (very similar to avro) as well as reflection
https://github.com/protocolbuffers/protobuf/blob/main/src/go...
Xgooglers trying to make do on the cheap will just create a Union of all their messages and include the message def in a self-describing message pattern. Super-sensitive network I/O can elide the message def (empty buffer) and any for RecordIO clone well file compression takes care of the definition.
Definitely useful to be able to dig out old defs but protobuf maintainers have surprisingly added useful features so you don’t have to.
Bonus points tho for extracting the protobuf defs that e.g. Apple bakes into their binaries.
- Show HN: AuthWin – Authenticator App for Windows
-
Create Production-Ready SDKs With gRPC Gateway
gRPC Gateway is a protoc plugin that reads gRPC service definitions and generates a reverse proxy server that translates a RESTful JSON API into gRPC.
-
Create Production-Ready SDKs with Goa
To use more recent versions of protoc in future applications, you can download them from the Protobuf repository.
-
Roll your own auth with Rust and Protobuf
Use the Protobuf CLI protoc and the plugin protoc-gen-tonic.
-
Add extra stuff to a “standard” encoding? Sure, why not
> didn’t find any standard for separating protobuf messages
The fact that protobufs are not self-delimiting is an endless source of frustration, but I know of 2 standards:
- SerializeDelimited* is part of the protobuf library: https://github.com/protocolbuffers/protobuf/blob/main/src/go...
- Riegeli is "a file format for storing a sequence of string records, typically serialized protocol buffers. It supports dense compression, fast decoding, seeking, detection and optional skipping of data corruption, filtering of proto message fields for even faster decoding, and parallel encoding": https://github.com/google/riegeli
-
Block YouTube Ads on AppleTV by Decrypting and Stripping Ads from Profobuf
It looks like it is in fact universal. Just glancing at the code here, it looks like the tool searches any arbitrary file for bytes that look like encoded protobuf descriptors, specifically looking for bytes that are plausibly the beginning of a FileDescriptorProto message defined here:
https://github.com/protocolbuffers/protobuf/blob/main/src/go...
This takes advantage of the fact that such descriptors are commonly compiled into programs that use protobuf. The descriptors are usually embedded as constant byte arrays. That said, not all protobuf implementations embed the descriptors and those that do often have an option to inhibit such embedding (at the expense of losing some dynamic introspection features).
- How to learn to use protoc in 21 easily infuriating steps
-
What's involved in protobuf encoding?
Not much. You can check the source code in https://github.com/protocolbuffers/protobuf. For example, for serializing a boolean in C#: https://github.com/protocolbuffers/protobuf/blob/main/csharp/src/Google.Protobuf/WritingPrimitives.cs#L165. Strings and objects are a bit more complicated, but it is all about turning the data into its byte representation.
What are some alternatives?
CLI11 - CLI11 is a command line parser for C++11 and beyond that provides a rich feature set with a simple and intuitive interface.
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library
Boost.Program_options - Boost.org program_options module
SBE - Simple Binary Encoding (SBE) - High Performance Message Codec
gflags - The gflags package contains a C++ library that implements commandline flags processing. It includes built-in support for standard types such as string and the ability to define flags in the source file in which they are used. Online documentation available at:
MessagePack - MessagePack implementation for C and C++ / msgpack.org[C/C++]
clipp - easy to use, powerful & expressive command line argument parsing for modern C++ / single header / usage & doc generation
cereal - A C++11 library for serialization
args - A simple header-only C++ argument parser library. Supposed to be flexible and powerful, and attempts to be compatible with the functionality of the Python standard argparse library (though not necessarily the API).
Apache Parquet - Apache Parquet
conan - Conan - The open-source C and C++ package manager
Bond - Bond is a cross-platform framework for working with schematized data. It supports cross-language de/serialization and powerful generic mechanisms for efficiently manipulating data. Bond is broadly used at Microsoft in high scale services.