bazel: make Starlark profiler work in Bazel Fixes https://github.com/bazelbuild/bazel/issues/10890 Details: - configure copybara so that Bazel sees JNI.java.oss as JNI.java. - use the correct .so library name for Bazel (no "-jni"). - add the dynamic library to to Bazel's install-base using the platform's required name (libx.so, libx.dylib, x.dll). - report errors during command startup, don't just store them. :) - don't consider SIG_DFL as "signal already in use". The pthreads package used by Bazel sets SIGPROF to DFL whereas Blaze's uses IGN. RELNOTES: The --starlark_cpu_profile=<file> flag writes a profile in pprof format containing a statistical summary of CPU usage by all Starlark execution during the bazel command. Use it to identify slow Starlark functions in loading and analysis. PiperOrigin-RevId: 315678587
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
