Buildifier feedback

This commit is contained in:
Greg Estren 2021-02-11 16:15:29 -05:00
parent 4e7e7f8cbb
commit f28c5e2e1b
2 changed files with 15 additions and 12 deletions

View File

@ -29,6 +29,8 @@
#
# This example demonstrates both approaches.
load("@rules_cc//cc:defs.bzl", "cc_library", "cc_toolchain", "cc_toolchain_suite")
# Load the Starlark logic defining the toolchain's behavior. For example: what
# program runs to compile a source file and how its command line is
# constructed. See toolchain_config.bzl for details.

View File

@ -1,15 +1,16 @@
# Sample Starlark definition defining a C++ toolchain's behavior.
#
# When you build a cc_* rule, this logic defines what programs run for what
# build steps (e.g. compile / link / archive) and how their command lines are
# structured.
#
# This is a proof-of-concept simple implementation. It doesn't construct fancy
# command lines and uses mock shell scripts to compile and link
# ("sample_compiler" and "sample_linker"). See
# https://docs.bazel.build/versions/master/cc-toolchain-config-reference.html and
# https://docs.bazel.build/versions/master/tutorial/cc-toolchain-config.html for
# advanced usage.
"""Sample Starlark definition defining a C++ toolchain's behavior.
When you build a cc_* rule, this logic defines what programs run for what
build steps (e.g. compile / link / archive) and how their command lines are
structured.
This is a proof-of-concept simple implementation. It doesn't construct fancy
command lines and uses mock shell scripts to compile and link
("sample_compiler" and "sample_linker"). See
https://docs.bazel.build/versions/master/cc-toolchain-config-reference.html and
https://docs.bazel.build/versions/master/tutorial/cc-toolchain-config.html for
advanced usage.
"""
load("@bazel_tools//tools/cpp:cc_toolchain_config_lib.bzl", "tool_path")