automatically including .pb.h files we depend on

[Alejandro Mery]

hi, I'm getting started trying to use nanopb for rpc between an embedded C application and a Go application.

I'm using `nanopb_generator -C` from the latest master, but the generated foo.pb.c on includes foo.pb.h, and that .h only includes pb.h itself. what's the correct way of getting the .pb.c to include the .pb.h files that define the types/structs we depend on?

`nanopb_generator -C nanopb.proto` itself produces a .pb.c that can't find `google_protobuf_field_descriptor_proto_type_t` as no where `google/protobuf/descriptor.pb.h` is included.

also, is there a way if specifying a prefix for those includes? it seem one can only customize pb.h include.

thanks in advance,

Alejandro Mery

[Alejandro Mery]

apologies for the self-reply.

On Monday, 6 November 2023 at 18:49:00 UTC Alejandro Mery wrote:

also, is there a way if specifying a prefix for those includes? it seem one can only customize pb.h include.

please disregard this part, `-Q` does that, but still only of the direct dependency

[Petteri Aimonen]

Hi,

> `nanopb_generator -C nanopb.proto` itself produces a .pb.c that can't find
> `google_protobuf_field_descriptor_proto_type_t` as no where
> `google/protobuf/descriptor.pb.h` is included.

Normally all imported .proto files generate corresponding includes of .pb.h files.

There are two proto files that are on default exclusion list, because
usually there is no need to include nanopb.proto or descriptor.proto in
the compiled C code, even though they are needed by protoc.

Custom includes of those or other files can be added by adding this near
the beginning of a .proto (or equivalently in .options file or -s on
command line):

option (nanopb_fileopt).include = 'foobar.h';

--
Petteri

[Alejandro Mery]

On Monday, 6 November 2023 at 19:00:21 UTC Petteri Aimonen wrote:

Hi,

> `nanopb_generator -C nanopb.proto` itself produces a .pb.c that can't find
> `google_protobuf_field_descriptor_proto_type_t` as no where
> `google/protobuf/descriptor.pb.h` is included.

Normally all imported .proto files generate corresponding includes of .pb.h files.

There are two proto files that are on default exclusion list, because
usually there is no need to include nanopb.proto or descriptor.proto in
the compiled C code, even though they are needed by protoc.

excellent, it all makes much more sense now

 

Custom includes of those or other files can be added by adding this near
the beginning of a .proto (or equivalently in .options file or -s on
command line):

option (nanopb_fileopt).include = 'foobar.h';

would you know the notation for fileopts on the options file? 

[Petteri Aimonen]

Hi,

> would you know the notation for fileopts on the options file?

* include:"foobar.h"

in place of wildcard you can also specify the proto file name.
Example e.g. here:
https://github.com/nanopb/nanopb/blob/master/examples/network_server/fileproto.options

--
Petteri