3 ms·

Bazel does not assume statically built. Where do you get this idea?

• saidinesh5 4y ago
  From their open issues and ugly hacks needed to build anything else... https://github.com/bazelbuild/bazel/issues/1920 https://github.com/bazelbuild/bazel/issues/1920 https://stackoverflow.com/questions/32845940/symbols-from-static-cc-library-dependency-in-so-missing https://stackoverflow.com/questions/32845940/symbols-from-st...
  • unicornmama 4y ago
    Those look like the problems with rules cc for building C++. But it’s not inherent to Bazel, and would not expect problems producing static binaries in other languages.
    • saidinesh5 4y ago
      That could be. We just had the ugly requirement of having to build a rust library/crate that uses C++ libraries (tensorflow lite + libedgetpu). That forced us to use bazel, on/for platforms that i have little experience / love for (Windows, Apple platforms). Hitting the platform annoyances of each of those platforms just added to the pain. (On Windows, the 260 character path limit + on iOS Apple messing with ar binary used to create static libraries). Left a very bad taste of trying to use bazel as a build tool. Even handwritten 1000+ lines of makefiles/experimental build systems like qbs did not cause so many headaches.