How to build without protobuf

[cvilas]

The readme says

eCAL is message protocol agnostic. You choose the message protocol that fits to your needs like Google Protobuf, CapnProto, Flatbuffers...

But, I am unable to build ecal from source without building protobuf or having protobuf on the host. It is actually possible?

[rex-schilasky]

Hi, current eCAL stable (5.13) is still using Protobuf for its own internal communication (discovery). So from user perspective you can 'use' eCAL with only Protobuf installed on your host.
Future eCAL version (eCAL6, release planned end of January) will use NanoPb Protobuf library statically linked. So the eCAL runtime has no more Protobuf dependencies finally.

[rex-schilasky]

Why do you build eCAL from source?

[cvilas]

Thanks @rex-schilasky. Will give eCAL 6 a go when it becomes available.

Why do you build eCAL from source?

A bit surprised by this question, to be honest. I thought this was standard across the industry. Both at work and for personal projects, I tend to build 'the world' from source, certainly for third-party dependencies of core libraries. Helps me control development environment and deployments across multiple targets and architectures.

[rex-schilasky]

Standard across the industry for sure but I assumed you just use it for a personal project.
Did you you succeed to build it finally?
eCAL 6 is worth to upgrade to. It will come with a renewed API as well as significant performance improvements.