Build optimization strategies for large C++ to WebAssembly projects

[e7h4n]

Hey everyone!

We're evaluating Bazel for our C++ to WebAssembly build pipeline and would love to learn from others' experiences.

Our current setup:

• Several hundred thousand lines of C++
• Compiling to WebAssembly via Emscripten
• Custom artifact caching system (reduced build time from 60min to 5min)
• 20+ developers, 2 production deploys daily

We're considering Bazel because our custom artifact cache is becoming hard to maintain. But converting third-party projects like Skia to Bazel seems extremely difficult. Skia uses GN, has tons of platform-specific code, and complex build configurations.

Has anyone successfully integrated large, complex C++ projects (especially Skia) into a Bazel build? We really want Bazel's caching benefits, but converting our dependencies feels like a massive undertaking. Any advice appreciated!