package used - protobuf-3.6.1-py37hf484d3e_0.tar.bz2 to build on x86
/root/anaconda3/conda-bld/protobuf_1543557438196/_build_env/bin/x86_64-conda_cos6-linux-gnu-cc
-DNDEBUG -fwrapv -O2 -Wall -Wstrict-prototypes -march=nocona -mtune=haswell
-ftree-vectorize -fPIC -fstack-protector-strong
On Wed, Nov 28, 2018 at 8:37 PM Chao-Hung Sun wrote:
>
> You were trying to access those .proto from raw source code,
Correct, and this is intentional. I would like to have our build
system pull the protos directly from their canonical source so that
they can be easily kept in sync with any
On Thu, Nov 29, 2018 at 1:08 PM Josh Humphries wrote:
>
> You know it's a message vs. enum (or invalid identifier) only after linking.
Thanks very much for the clarification. I sort of figured that was the case.
> To link, you need the file's entire transitive closure (e.g. its imports and
>
You know it's a message vs. enum (or invalid identifier) only after linking.
To link, you need the file's entire transitive closure (e.g. its imports
and their imports and so on) already parsed (and, preferably, already
linked). You can then *resolve* the type name, basically using C++ scoping
Hello,
In the Protocol Buffer v2 Field specification there is a notion of
messageType and enumType. Casually reading the specification, it is
easy to miss this, but there is nothing there to tell anyone whether a
messageType or an enumType was encountered, except perhaps a second
pass
