[protobuf] Re: How Do I Build Just the C++ Libraries?

2017-03-17 Thread 'Josh Haberman' via Protocol Buffers
Try: $ cd src && make libprotobuf.la libprotobuf-lite.la I can't guarantee it will compile without fork(), but it should avoid compiling the compiler! On Tuesday, March 14, 2017 at 2:01:43 PM UTC-7, Doug Lewis wrote: > > I'm going to be using protocol buffers on an embedded system using >

[protobuf] Re: Disable arena During Build Process

2017-03-17 Thread 'Josh Haberman' via Protocol Buffers
I don't think there is a way to disable arenas. But this error looks like it is related to thread-local storage. You could try compiling with GOOGLE_PROTOBUF_NO_THREADLOCAL and see if that helps: $ ./configure CPPFLAGS=-DGOOGLE_PROTOBUF_NO_THREADLOCAL On Wednesday, March 15, 2017 at 6:51:42 AM

[protobuf] Re: Protocol buffer classes are basically dumb data holders (like structs in C++);

2017-03-17 Thread 'Josh Haberman' via Protocol Buffers
Can you be more specific about what you think needs fixing? I think the docs are saying that the generated classes don't have any business logic in them. This is true and seems clear to me. On Thursday, March 16, 2017 at 8:29:00 AM UTC-7, Dimitris Servis wrote: > > Hmmm? > > documentation needs

[protobuf] Re: go protobuf: "rich" descriptors

2017-03-17 Thread 'Damien Neil' via Protocol Buffers
That looks very nice! I've written ad-hoc versions of that a couple times for very specific use cases, but your package seems to be quite complete. I think it would be better off remaining a third-party library for now, at least. While the Go protobuf repo can accept external contributions,