On Wed, Jan 5, 2011 at 10:33 PM, Scratch wrote:
> Thanks!
> That's right what I needed. And one more question - will sub-builders
> be introduced for lite package?
>
Sorry, but probably not. The whole point of the lite package is to be as
small as possible, and the sub-builders stuff creates a
On Mon, Jan 10, 2011 at 9:45 PM, Nicolae Mihalache wrote:
> Hello,
>
> I recently started to use GPB, great software! :)
>
> But I have noticed in java that it is impossible to create a message
> containing a "bytes" fields without copying some buffers around. For
> example if I have a encoded mes
Oh, you meant that they are *not* installed.
These two files are private interfaces. They have LIBPROTOBUF_EXPORT on
them because libprotoc uses them. However, other clients are not meant to
use these headers.
On Mon, Jan 10, 2011 at 11:46 AM, Collin wrote:
> The following headers have LIBPRO
OK. What is the problem?
On Mon, Jan 10, 2011 at 11:46 AM, Collin wrote:
> The following headers have LIBPROTOBUF_EXPORT in them but are
> installed with `make install.`
>
> google/protobuf/stubs/strutil.h
> google/protobuf/stubs/substitute.h
>
> --
> You received this message because you are s
Can you provide a small, self-contained example?
On Mon, Jan 10, 2011 at 7:13 AM, Meghana wrote:
> Hi,
>
> I am using imports in my proto files. So, B has an import of A. When I
> generate the java code for B, all references to A are specified as A.A
> i.e. A(dot)A. It does not seem to be picking
I see, I think the encoding problem was fixed in 2.3.0.
The type checker is still wrong, though.
On Thu, Jan 6, 2011 at 3:17 PM, BigBaaadBob wrote:
> 2.2.0a-0.1ubuntu1
>
> On Dec 28 2010, 2:55 pm, Kenton Varda wrote:
> > Strange. It looks like there is a bug in the type checker for booleans
>
On Tue, Jan 11, 2011 at 1:30 PM, Collin wrote:
> I am trying to understand how --proto_path works. Let's say in
> my .proto file have the following import lines:
> import "descriptor.proto";
> import "google/protobuf/descriptor.proto";
>
Delete the first of these two imports, and then use
--prot
On Jan 11, 9:25 pm, Evan Jones wrote:
> This is a disadvantage, but it makes things much easier: it means the
> buffer used to read data can be recycled for the next message. Without
> this copy, the library would need to do complicated tracking of chunks
> of memory to determine if they are
I am trying to understand how --proto_path works. Let's say in
my .proto file have the following import lines:
import "descriptor.proto";
import "google/protobuf/descriptor.proto";
What would the path be for the option?
I have tried using different path:
protoc --proto_path=/usr/local/include/g
On Jan 11, 2011, at 0:45 , Nicolae Mihalache wrote:
But I have noticed in java that it is impossible to create a message
containing a "bytes" fields without copying some buffers around. For
example if I have a encoded message of 1MB with a few regular fields
and one big bytes field, decoding the
Comment #28 on issue 66 by jparise: cannot install using easy_install
http://code.google.com/p/protobuf/issues/detail?id=66
Timothee Peignier's patch is very helpful. It extended his work with the
attached patch to cover one more remaining issue.
The 'clean' step was always removing generat
Hello,
I recently started to use GPB, great software! :)
But I have noticed in java that it is impossible to create a message
containing a "bytes" fields without copying some buffers around. For
example if I have a encoded message of 1MB with a few regular fields
and one big bytes field, decoding
12 matches
Mail list logo
