Age | Commit message (Collapse) | Author | Files | Lines |
|
Now -e option in generator is more versatile. Especially it avoids
double-dot problem with some build systems.
Given foobar.proto, we now get:
-e .pb => foobar.pb.c (default)
-e _pb => foobar_pb.c
-e '' => foobar.c
Note that if you have used -e option previously, you will have to prepend
. to the argument to get the same filenames as before.
Update issue 122
Status: FixedInGit
|
|
Update issue 124
Status: FixedInGit
|
|
The options for an extension field were being looked up under wrong name
(MessageName instead of MessageName.fieldname).
Fixed the problem and added regression test. Created a new subfolder for
regression test cases.
Update issue 125
Status: FixedInGit
|
|
|
|
|
|
Patch by rusnakp.
Update issue 115
Status: FixedInGit
|
|
|
|
|
|
Update issue 111
Status: FixedInGit
|
|
This makes the internal logic much simpler, and also keeps the datatypes
more similar between STATIC/POINTER cases. It will still be a bit cumbersome
to use because of variable length array member. Macros PB_BYTES_ARRAY_T(n) and
PB_BYTES_ARRAY_T_ALLOCSIZE(n) have been added to make life a bit easier.
This has the drawback that it is no longer as easy to use externally allocated
byte array as input for bytes field in pointer mode. However, this is still
easy to do using callbacks, so it shouldn't be a large issue.
|
|
|
|
|
|
This fixes some interoperability problems when trying to compile
nanopb.proto for e.g. the Google's C++ library.
Update issue 104
Status: FixedInGit
|
|
Update issue 105
Status: FixedInGit
|
|
Update issue 96
Status: FixedInGit
|
|
Update issue 102
Status: FixedInGit
|
|
|
|
|
|
|
|
|
|
Otherwise they won't be visible when run as a protoc plugin.
|
|
|
|
|
|
versions.
|
|
Allocation decision is now made before the field data type is decided.
This way the data type decisions can more cleanly account for the allocation
type, i.e. FT_DEFAULT logic etc.
Added pb_bytes_ptr_t for pointer-allocated bytes-fields. There is no point
generating separate structs for these, as they would all be of the same type.
|
|
|
|
|
|
|
|
|
|
Update issue 93
Status: FixedInGit
|
|
|
|
|
|
|
|
Add testcase for the same.
|
|
Update issue 89
Status: FixedInGit
|
|
|
|
|
|
Requires re-generation of files generated with dev_get_rid_of_ternary_operator.
|
|
Some compilers where unable to detect that the ternary operator
can be evaluated at the compile time. This commit does the evaluation
on the Python side, which should fix the problem.
The new .pb.c files are generated using PB_FIELD2() macro. The old
PB_FIELD() macro remains, so that previously generated files keep
working.
|
|
Will be used to implement issue 47.
For now, symlink nanopb_generator.py as protoc-gen-nanopb and
use protoc --nanopb_out=. to call it.
|
|
Previously the generator would stop with NotImplementedException as
soon as a required or repeated extension field is found. New behaviour
is to just ignore the unsupported field and note that in a comment
in the generated file.
Furthermore, allow skipping of extension fields using the generator
option (nanopb).type = FT_IGNORE.
Update issue 83
Status: FixedInGit
|
|
|
|
|
|
|
|
Testing is still needed. Also only 'optional' extension fields
are supported now, 'repeated' fields are not yet supported.
|
|
yet)
|
|
Patch from Michael Haberler.
|
|
|
|
|
|
The arg field can be used to store the field presence from inside
the callback. Furthermore, having the has_ field for encoding callbacks
would be more annoying than useful.
Update issue 70
Status: FixedInGit
|