It looks to me like you don't have the protocol-buffers package
installed. It is required to build protobuf-c.
I guess I need to add a autoconf test to make it clear that that's
necessary.
- dave
On Sep 29, 2:05 am, Doron Tal <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm new to protobuf, and I want
I'd be wary about getting into too custom of applications here.
People should make their own configuration files for GUI generator and
caches, in my opinion; they're too complex and special-purpose and so
on. For example, GUIs require more layout information than "render as
slider" or something--
you could consider wrapping protobuf-c... that will at least save you
the hassle of writing the C wrapper around C++.
- dave
On Nov 12, 10:04 am, "Petar Petrov" <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 9, 2008 at 5:14 PM, codeazure <[EMAIL PROTECTED]> wrote:
>
> > On Oct 31, 5:19 am, "Petar Petr
The reason why it is crashing is that all messages have a few builtin
members that are usually initialized via ITEM__INIT. If you look at
the generated Item it looks like:
struct _Item
{
ProtobufCMessage base_message;
uint32_t id;
};
The best way to construct a message is to use C
niggling
issues, but i've now got the design in my head, and the coding should
be pretty easy)
- dave
On Nov 27, 7:42 pm, daveb <[EMAIL PROTECTED]> wrote:
> The reason why it is crashing is that all messages have a few builtin
> members that are usually initialized via ITEM__INIT.
BTW: I just released protobuf-c 0.6 which include the item__init()
function (and it also supports default-values properly now).
- dave
On Nov 27, 7:48 pm, daveb <[EMAIL PROTECTED]> wrote:
> I should mention too: I plan to eventually add a generated function
> "item__init(Item
Well, I've been working out how a RPC impl will look in C, and I
decided that rather than use some inappropriate (TCP) or unreliable
(UDP) transport, I would go with the new kid, SCTP.
SCTP is a reliable datagram protocol that layers over IPv4 or IPV6,
and is at the same level as TCP or UDP. Ther
Well, I've been working out how a RPC impl will look in C, and I
decided that rather than use some inappropriate (TCP) or unreliable
(UDP) transport, I would go with the new kid, SCTP.
SCTP is a reliable datagram protocol that layers over IPv4 or IPV6,
and is at the same level as TCP or UDP. Ther
Just got a complaint from a user saying that they needed to add -
lpthread to link against protoc.
I hadn't heard of the pthread change by the way -- was that expected?
It might be nice if there was a pkg-config file for protoc so that -
lpthread can be sucked up exactly when needed.
--~--~--
Well, you really have too different problems... the test code isn't
working basically because of some sort of configure issue. I don't
know why but configure isn't finding your "protoc" program (it uses
protoc b/c it generates c++ code to compare the packed data with the c
code's packed data)...
patch, which is applied in the latest protobuf-c,
the recently released 0.11.
- dave
On Jun 10, 3:04 pm, daveb wrote:
> Well, you really have too different problems... the test code isn't
> working basically because of some sort of configure issue. I don't
> know why but conf
Protobuf-c has a small bit in its test-suite that uses protobuf's c++
binding to generate packed versions of several messages that are
compared with c binding packed data.
I'm almost tempted to get rid of these fragile tests b/c they are such
a build annoyance. But I'm going to try to keep them
I admit: I could have been a little more clever in the name.
But if you are interested in protobuf-c, or if you have questions
specific to these C bindings, please use that forum! That way, I'll
see it...
Here's the link: http://groups.google.com/group/protobuf-c/
cheers,
dave
--
You receiv
13 matches
Mail list logo
