Now on to linking.... 98 independent absl static libs? Really? Would it not be possible to simply combine the ones protobuf is dependent on?
In another post there was a mention about this being "bad practice". In who's world is it bad practice to make it easy to use a third party library? On Friday, February 14, 2025 at 7:32:49 AM UTC-8 Brian Sassone wrote: > Better luck today using top of tree. Branch 29.3 build seems broken in > various ways. Here's what worked using cmake: > > git clone --depth 1 https://github.com/protocolbuffers/protobuf.git > cd protobuf > mkdir build > cd build > cmake \ > -Dprotobuf_BUILD_TESTS=OFF \ > -Dprotobuf_BUILD_EXAMPLES=OFF \ > -Dprotobuf_BUILD_SHARED_LIBS=OFF \ > -DCMAKE_CXX_STANDARD=17 \ > .. > make > > > On Friday, February 14, 2025 at 2:03:30 AM UTC-8 Brian Sassone wrote: > >> Is it possible to build the runtime as a static lib? If so, how do I do >> this with bazel? There is no applicable target and this build system is >> not something I'm familiar with. >> >> Tried using cmake, but that brings up a whole slew of other issues. Sigh. >> >> I've compiled all kinds of 3rdparty packages on various OS's and have >> never struggled like this. Very frustrating. >> >> -b >> > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/protobuf/1fb3f116-85ac-4ca4-8943-202036eea53dn%40googlegroups.com.
