Home
last modified time | relevance | path

Searched refs:all (Results 1 – 25 of 33) sorted by relevance

12

/nanopb-3.4.0/generator/proto/
DMakefile3 all: nanopb_pb2.py target
Dnanopb.proto46 // a field. When it is used in message or file scope, it applies to all
121 // will be called for all callback fields in a message type.
166 // Extensions: 1010 (all types)
/nanopb-3.4.0/tests/alltypes_proto3_callback/
Dalltypes.options1 # Generate all fields as callbacks.
DSConscript1 # Test the AllTypes encoding & decoding using callbacks for all fields.
/nanopb-3.4.0/tests/io_errors_pointers/
Dalltypes.options1 # Generate all fields as pointers.
/nanopb-3.4.0/tests/fuzztest/
Dalltypes_pointer.options1 # Generate all fields as pointers.
/nanopb-3.4.0/tests/alltypes_callback/
Dalltypes.options1 # Generate all fields as callbacks.
DSConscript1 # Test the AllTypes encoding & decoding using callbacks for all fields.
/nanopb-3.4.0/examples/network_server/
DMakefile8 all: server client target
/nanopb-3.4.0/examples/using_union_messages/
DMakefile8 all: encode decode target
Dunionproto.proto2 // with nanopb, without allocating memory for all the message types.
DREADME.txt11 all of the possible messages at the same time, even though at most one of
/nanopb-3.4.0/tests/alltypes_pointer/
Dalltypes.options1 # Generate all fields as pointers.
DSConscript1 # Encode the AllTypes message using pointers for all fields, and verify the
/nanopb-3.4.0/tests/regression/issue_242/
DSConscript2 # extension fields that is all zeros
/nanopb-3.4.0/tests/
DMakefile1 all: target
/nanopb-3.4.0/tests/docker_images/
DREADME.md13 To build tests for all targets, use:
/nanopb-3.4.0/docs/
DMakefile3 all: $(INPUTS:.md=.html) target
Dindex.md54 7) Support for most protobuf features, including: all data types,
137 custom include file, which should provide all the dependencies listed
156 [pip](https://pypi.org/project/pip/), which works on all platforms supported by Python:
Dconcepts.md26 protoc version 3.6 or newer to support all features, and some distributions come with an older
229 …ixed_count` repeated field at a time. Usually this it not an issue because all elements of a repea…
270 `repeated` field, you should do it all in a single call.
312 function over and over until all values have been read.
357 description of all the fields contained in a message. This description
540 user, as there is no one-size-fits-all solution. Typical needs for a
548 For example UDP packets already fulfill all the requirements, and TCP
593 it for some reason. Often resolved by giving all `.proto` files as argument
Dlsr.css5 Copyright: This stylesheet has been placed in the public domain - free to edit and use for all uses.
Dmigration.md3 This document details all the breaking changes that have been made to
77 file at all. If your `.proto` files import it, change to using `generator/proto/nanopb.proto`.
132 submessage type and array size for all fields, even though most fields
465 **Required actions:** Regenerate all `.pb.h` files. In some cases casts
497 **Required actions:** Regenerate all `.pb.c` files. If you use any of
592 initializers in the .pb.c file. This led to a need to regenerate all
600 **Required actions:** Regenerate all .pb.c files from the .proto
/nanopb-3.4.0/tests/alltypes/
DSConscript2 # all of the Protocol Buffers data types.
/nanopb-3.4.0/
DREADME.md35 format that is compatible with all Protocol Buffers libraries. To use it with nanopb,
44 The binary packages for Windows, Linux and Mac OS X should contain all necessary
/nanopb-3.4.0/extra/
DFindNanopb.cmake24 # This causes all output files to go directly
47 # option. The argument to RELPATH should be the directory that all the
49 # When RELPATH is not specified then all proto files can be imported without

12