Build profiles
The cargo profiles of development, release, and profiling builds.
dev(just build,just run, the tests): unoptimized workspace crates, dependencies atopt-level = 2, full debug info. Every build forx86_64-unknown-linux-gnu, the development builds included, compiles Rust and C code for the CPU level of the shipped x86_64 binaries, x86-64-v2 (.cargo/config.toml)dev-opt(just run-dev-opt):devwith optimized workspace crates, for long runs on real datasets; rebuilds are slowerrelease(just build-release,just run-release,just example,just smoke): optimized and fast to rebuild, without LTOdist(just build-dist,just cross,just build-napi dist,just cross-napi, nightly releases): the shipped binary and Node addon, with fat LTO, one codegen unit, and the CPU and link flags of the shipped builds fromexport_dist_flagsofdev/lib/dist-flags.sh(-C target-cpu=x86-64-v2on x86-64, no frame pointers). These flags replace the target rustflags of the Cargo config files, so the native dist builds link with rust-lld. The glibc binaries ofbuild-dist,build-profiling,build-profiling-heap, andbenchlink the GCC unwinder statically and need nolibgcc_s.so.1, as the cross builds do; the Node addon keeps the shared unwinder of the Electron processprofiling(just build-profiling,just profile):distwith full debug info; without frame pointers, profilers unwind call stacks with DWARF (dev/profiledoes) or LBRprofiling-heap(just build-profiling-heap):profilingwith jemalloc heap profiling compiled in, for heap profiles onlybench(just bench): thedistsettings