This will allow message sizes and enum options to be available
across the include files.

Currently searching for .options files for included files may
not work for all path combinations, this is related to issue #116.
Should probably make a pull request to protoc about that.

In preparation for multi-file support in generator.
No functional changes yet.

Previously unsigned enums would throw errors on decoding if the value
went outside the signed range (issue #164).

Currently only helps for enums defined within the same file, but solving
issue #165 will make it work for multiple files also.

This can be generally useful for saving RAM, but also makes
it easier to test for issue #164.

Specify additional fields for @PlatformIO Registry

PlatformIO Library Registry manifest file

Update issue 155
Status: FixedInGit

Update issue 154
Status: FixedInGit

Update issue 153
Status: FixedInGit

Update issue 148
Status: FixedInGit

Update issue 145
Status: FixedInGit

Update issue 118
Status: FixedInGit

This handles special charaters like in "my-file.proto" properly.
Also use headerbasename instead of full path, so that compiling files
with relative path doesn't create symbols like FOO/BAR/BAZ_MESSAGES.

Update issue 149
Status: FixedInGit

Update issue 147
Status: FixedInGit

Previously this got included by bbfreeze, but apparently no more.

Update issue 146
Status: FixedInGit

Do not assume that Python has already been found by CMake. Fix value of
CMake variable PYTHON_EXECUTABLE if Python 3 was found. Change minimum
supported Python version to 2.6.

This fixes a bug introduced by this commit:
d8d3b75e

1) Search explicitly for python2.7

In systems where python3 is default or in build cases where the user has
already searched for and found python3 in CMake, store the python3
executable and search for python2.7.

2) Generate nanopb core protobuf files with CMake

Generate python output files used in turn by the nanopb generator
script. This removes the requirement of manually calling 'make' in the
nanopb/generator/proto directory.

3) Use nanopb options file if it exists

Look for nanopb options file and use in protobuf source and header
generation if it exists. The options file must have the same name and
path as the proto file, excluding the extension.