Googler d8dfa8b829 Introduce flag --@rules_cc//:link_extra_libs ... Numerous tools override --custom_malloc to add debugging or monitoring runtimes (see e.g. sanitizers). While this is fine for cases where the tool must also override malloc to function, in other cases it's simply misuse of --custom_malloc where no other mechanism exists to link an extra library. This becomes especially problematic where a runtime library is supposed to be added in certain configurations that should run in production or other performance sensitive builds. In these cases, we should _not_ override malloc, which may also be specified by a cc_binary target. Doing so would introduce unwanted changes, potentially affecting performance negatively. This is the @rules_cc counterpart to the equivalent Bazel tools flag --@bazel_tools//tools/cpp:link_extra_libs. Users that use @rules_cc to build their C++ projects may use both flags interchangably, however, the @rules_cc flag should be preferred. PiperOrigin-RevId: 510103352 Change-Id: Iafccd00ffdb65cb4f953d5acadc451cffc134533		2023-02-16 04:15:10 -08:00
..
BUILD	Introduce flag --@rules_cc//:link_extra_libs	2023-02-16 04:15:10 -08:00
foo.cc	Introduce flag --@rules_cc//:link_extra_libs	2023-02-16 04:15:10 -08:00