A unique name for this target.

Specify the name of the created .a file (that is decoupled from the rule instance name).
Note, that the 'cc_archive' is opinionated and will remove any leading 'lib' prefix and any '.a' in the name
(meaning 'libTest.a.x64.a' will become 'Test.x64' and will produce 'libTest.x64.a')

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

The list of source files.

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

List of headers that CANNOT be included by dependent rules.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

The list of files that are regarded as C++20 Modules Interface.

C++ Standard has no restriction about module interface file extension

• Clang use cppm
• GCC can use any source file extension
• MSVC use ixx

The use is guarded by the flag --experimental_cpp_modules.

The Windows DEF file to be passed to linker.

This attribute should only be used when Windows is the target platform. It can be used to export symbols during linking a shared library.

Any additional files you might want to pass to the compiler command line, such as sanitizer ignorelists, for example.
Files specified here can then be used in copts with the $(location) function.

Any additional files that you may want to pass to the linker, for example, linker scripts.
You have to separately pass any linker flags that the linker needs in order to be aware of this file.
You can do so via the linkopts attribute.

Add these options to the C compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.
Each string in this attribute is added in the given order to COPTS before compiling the binary target. The flags take effect only for compiling this target, not its dependencies, so be careful about header files included elsewhere. All paths should be relative to the workspace, not to the current package.

If the package declares the feature no_copts_tokenization, Bourne shell tokenization applies only to strings that consist of a single "Make" variable.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line to this target, as well as to every rule that depends on it. Be very careful, since this may have far-reaching effects. When in doubt, add define values to local_defines instead.

In contrast to rules_cc, the dynamic_deps of rules_cc_hdrs_map are simply translated into deps parameter,
and the providers (CcInfo vs CcSharedInfo) are used to steer the behavior further.

The list of other libraries that the library target depends on. Unlike with deps, the headers and include paths of these libraries (and all their transitive deps) are only used for compilation of this library, and not libraries that depend on it. Libraries specified with implementation_deps are still linked in binary targets that depend on this library.

List of include dirs to be added to the compile line.
Subject to "Make variable" substitution. Each string is prepended with -isystem and added to COPTS. Unlike COPTS, these flags are added for this rule and every rule that depends on it. (Note: not the rules it depends upon!) Be very careful, since this may have far-reaching effects. When in doubt, add "-I" flags to COPTS instead.

Headers must be added to srcs or hdrs, otherwise they will not be available to dependent rules when compilation is sandboxed (the default).

Add these flags to the C++ linker command. Subject to "Make" variable substitution, Bourne shell tokenization and label expansion. Each string in this attribute is added to LINKOPTS before linking the binary target.
Each element of this list that does not start with $ or - is assumed to be the label of a target in deps. The list of files generated by that target is appended to the linker options. An error is reported if the label is invalid, or is not declared in deps.

Create a shared library. To enable this attribute, include linkshared=True in your rule. By default this option is off.

Simultaneously compiles and links the specified C++ source file into the final binary. This trickery is required to introduce timestamp information into binaries; if we compiled the source file to an object file in the usual way, the timestamp would be incorrect. A linkstamp compilation may not include any particular set of compiler flags and so should not depend on any particular header, compiler option, or other build variable. This option should only be needed in the base package.

If enabled and this is a binary or test, this option tells the build tool to link in .a's instead of .so's for user libraries whenever possible. System libraries such as libc (but not the C/C++ runtime libraries, see below) are still linked dynamically, as are libraries for which there is no static library. So the resulting executable will still be dynamically linked, hence only mostly static.
The linkstatic attribute has a different meaning if used on a cc_library() rule. For a C++ library, linkstatic=True indicates that only static linking is allowed, so no .so will be produced. linkstatic=False does not prevent static libraries from being created. The attribute is meant to control the creation of dynamic libraries.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line for this target, but not to its dependents.

Remove matching options from the C++ compilation command. Subject to "Make" variable substitution. The value of this attribute is interpreted as a regular expression. Any preexisting COPTS that match this regular expression (including values explicitly specified in the rule's copts attribute) will be removed from COPTS for purposes of compiling this rule. This attribute should not be needed or used outside of third_party. The values are not preprocessed in any way other than the "Make" variable substitution.

The prefix to add to the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at is the value of this attribute prepended to their repository-relative path.

The prefix in the strip_include_prefix attribute is removed before this prefix is added.

The prefix to strip from the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at their path with this prefix cut off.

If it's a relative path, it's taken as a package-relative one. If it's an absolute one, it's understood as a repository-relative path.

The prefix in the include_prefix attribute is added after this prefix is stripped.

The list of header files published by this library to be textually included by sources in dependent rules.

This is the location for declaring header files that cannot be compiled on their own; that is, they always need to be textually included by other source files to build valid code.

A unique name for this target.

Whether to encode build information into the binary. Possible values:

• stamp = 1: Always stamp the build information into the binary, even in --nostamp builds. This setting should be avoided, since it potentially kills remote caching for the binary and any downstream actions that depend on it.

• stamp = 0: Always replace build information by constant values. This gives good build result caching.

• stamp = -1: Embedding of build information is controlled by the --[no]stamp flag.

Stamped binaries are not rebuilt unless their dependencies change.

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

The list of source files.

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

The list of files that are regarded as C++20 Modules Interface.

C++ Standard has no restriction about module interface file extension

• Clang use cppm
• GCC can use any source file extension
• MSVC use ixx

The use is guarded by the flag --experimental_cpp_modules.

The Windows DEF file to be passed to linker.

This attribute should only be used when Windows is the target platform. It can be used to export symbols during linking a shared library.

Any additional files you might want to pass to the compiler command line, such as sanitizer ignorelists, for example.
Files specified here can then be used in copts with the $(location) function.

Any additional files that you may want to pass to the linker, for example, linker scripts.
You have to separately pass any linker flags that the linker needs in order to be aware of this file.
You can do so via the linkopts attribute.

Add these options to the C compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.
Each string in this attribute is added in the given order to COPTS before compiling the binary target. The flags take effect only for compiling this target, not its dependencies, so be careful about header files included elsewhere. All paths should be relative to the workspace, not to the current package.

If the package declares the feature no_copts_tokenization, Bourne shell tokenization applies only to strings that consist of a single "Make" variable.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line to this target, as well as to every rule that depends on it. Be very careful, since this may have far-reaching effects. When in doubt, add define values to local_defines instead.

In contrast to rules_cc, the dynamic_deps of rules_cc_hdrs_map are simply translated into deps parameter,
and the providers (CcInfo vs CcSharedInfo) are used to steer the behavior further.

List of include dirs to be added to the compile line.
Subject to "Make variable" substitution. Each string is prepended with -isystem and added to COPTS. Unlike COPTS, these flags are added for this rule and every rule that depends on it. (Note: not the rules it depends upon!) Be very careful, since this may have far-reaching effects. When in doubt, add "-I" flags to COPTS instead.

Headers must be added to srcs or hdrs, otherwise they will not be available to dependent rules when compilation is sandboxed (the default).

Control linking of extra libraries.

By default, C++ binaries are linked against //tools/cpp:link_extra_lib, which by default depends on the label flag //tools/cpp:link_extra_libs. Without setting the flag, this library is empty by default. Setting the label flag allows linking optional dependencies, such as overrides for weak symbols, interceptors for shared library functions, or special runtime libraries (for malloc replacements, prefer malloc or --custom_malloc). Setting this attribute to None disables this behaviour.

Add these flags to the C++ linker command. Subject to "Make" variable substitution, Bourne shell tokenization and label expansion. Each string in this attribute is added to LINKOPTS before linking the binary target.
Each element of this list that does not start with $ or - is assumed to be the label of a target in deps. The list of files generated by that target is appended to the linker options. An error is reported if the label is invalid, or is not declared in deps.

Create a shared library. To enable this attribute, include linkshared=True in your rule. By default this option is off.

If enabled and this is a binary or test, this option tells the build tool to link in .a's instead of .so's for user libraries whenever possible. System libraries such as libc (but not the C/C++ runtime libraries, see below) are still linked dynamically, as are libraries for which there is no static library. So the resulting executable will still be dynamically linked, hence only mostly static.
The linkstatic attribute has a different meaning if used on a cc_library() rule. For a C++ library, linkstatic=True indicates that only static linking is allowed, so no .so will be produced. linkstatic=False does not prevent static libraries from being created. The attribute is meant to control the creation of dynamic libraries.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line for this target, but not to its dependents.

Override the default dependency on malloc.

By default, C++ binaries are linked against //tools/cpp:malloc, which is an empty library so the binary ends up using libc malloc. This label must refer to a cc_library. If compilation is for a non-C++ rule, this option has no effect. The value of this attribute is ignored if linkshared=True is specified.

Remove matching options from the C++ compilation command. Subject to "Make" variable substitution. The value of this attribute is interpreted as a regular expression. Any preexisting COPTS that match this regular expression (including values explicitly specified in the rule's copts attribute) will be removed from COPTS for purposes of compiling this rule. This attribute should not be needed or used outside of third_party. The values are not preprocessed in any way other than the "Make" variable substitution.

A unique name for this target.

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

List of headers that CANNOT be included by dependent rules.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

The list of files that are regarded as C++20 Modules Interface.

C++ Standard has no restriction about module interface file extension

• Clang use cppm
• GCC can use any source file extension
• MSVC use ixx

The use is guarded by the flag --experimental_cpp_modules.

The Windows DEF file to be passed to linker.

This attribute should only be used when Windows is the target platform. It can be used to export symbols during linking a shared library.

A unique name for this target.

If 1, any binary that depends (directly or indirectly) on this C++ precompiled library will link in all the object files archived in the static library, even if some contain no symbols referenced by the binary. This is useful if your code isn't explicitly called by code in the binary, e.g., if your code registers to receive some callback provided by some service.

This attribute contains a list of targets that are claimed to be exported by the current shared library.

Any target deps is already understood to be exported by the shared library. This attribute should be used to list any targets that are exported by the shared library but are transitive dependencies of deps.

Note that this attribute is not actually adding a dependency edge to those targets, the dependency edge should instead be created by deps.The entries in this attribute are just strings. Keep in mind that when placing a target in this attribute, this is considered a claim that the shared library exports the symbols from that target. The cc_shared_library logic doesn't actually handle telling the linker which symbols should be exported.

The following syntax is allowed:

//foo:pkg to account for any target in foo/BUILD

//foo:subpackages to account for any target in foo/BUILD or any other package below foo/ like foo/bar/BUILD

(Not yet implemented)

Specify the name of the created SOL file (that is decoupled from the rule instance name).
Note, that the 'cc_so' is opinionated and will remove any leading 'lib' prefix and any '.so' in the name
(meaning 'libTest.so.x64.so' will become 'Test.x64' and will produce 'libTest.x64.so')

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

The list of source files.

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

List of headers that CANNOT be included by dependent rules.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

The list of files that are regarded as C++20 Modules Interface.

C++ Standard has no restriction about module interface file extension

• Clang use cppm
• GCC can use any source file extension
• MSVC use ixx

The use is guarded by the flag --experimental_cpp_modules.

The Windows DEF file to be passed to linker.

This attribute should only be used when Windows is the target platform. It can be used to export symbols during linking a shared library.

Any additional files you might want to pass to the compiler command line, such as sanitizer ignorelists, for example.
Files specified here can then be used in copts with the $(location) function.

Any additional files that you may want to pass to the linker, for example, linker scripts.
You have to separately pass any linker flags that the linker needs in order to be aware of this file.
You can do so via the linkopts attribute.

Add these options to the C compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.
Each string in this attribute is added in the given order to COPTS before compiling the binary target. The flags take effect only for compiling this target, not its dependencies, so be careful about header files included elsewhere. All paths should be relative to the workspace, not to the current package.

If the package declares the feature no_copts_tokenization, Bourne shell tokenization applies only to strings that consist of a single "Make" variable.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line to this target, as well as to every rule that depends on it. Be very careful, since this may have far-reaching effects. When in doubt, add define values to local_defines instead.

In contrast to rules_cc, the dynamic_deps of rules_cc_hdrs_map are simply translated into deps parameter,
and the providers (CcInfo vs CcSharedInfo) are used to steer the behavior further.

The list of other libraries that the library target depends on. Unlike with deps, the headers and include paths of these libraries (and all their transitive deps) are only used for compilation of this library, and not libraries that depend on it. Libraries specified with implementation_deps are still linked in binary targets that depend on this library.

List of include dirs to be added to the compile line.
Subject to "Make variable" substitution. Each string is prepended with -isystem and added to COPTS. Unlike COPTS, these flags are added for this rule and every rule that depends on it. (Note: not the rules it depends upon!) Be very careful, since this may have far-reaching effects. When in doubt, add "-I" flags to COPTS instead.

Headers must be added to srcs or hdrs, otherwise they will not be available to dependent rules when compilation is sandboxed (the default).

Control linking of extra libraries.

By default, C++ binaries are linked against //tools/cpp:link_extra_lib, which by default depends on the label flag //tools/cpp:link_extra_libs. Without setting the flag, this library is empty by default. Setting the label flag allows linking optional dependencies, such as overrides for weak symbols, interceptors for shared library functions, or special runtime libraries (for malloc replacements, prefer malloc or --custom_malloc). Setting this attribute to None disables this behaviour.

Add these flags to the C++ linker command. Subject to "Make" variable substitution, Bourne shell tokenization and label expansion. Each string in this attribute is added to LINKOPTS before linking the binary target.
Each element of this list that does not start with $ or - is assumed to be the label of a target in deps. The list of files generated by that target is appended to the linker options. An error is reported if the label is invalid, or is not declared in deps.

Create a shared library. To enable this attribute, include linkshared=True in your rule. By default this option is off.

Simultaneously compiles and links the specified C++ source file into the final binary. This trickery is required to introduce timestamp information into binaries; if we compiled the source file to an object file in the usual way, the timestamp would be incorrect. A linkstamp compilation may not include any particular set of compiler flags and so should not depend on any particular header, compiler option, or other build variable. This option should only be needed in the base package.

If enabled and this is a binary or test, this option tells the build tool to link in .a's instead of .so's for user libraries whenever possible. System libraries such as libc (but not the C/C++ runtime libraries, see below) are still linked dynamically, as are libraries for which there is no static library. So the resulting executable will still be dynamically linked, hence only mostly static.
The linkstatic attribute has a different meaning if used on a cc_library() rule. For a C++ library, linkstatic=True indicates that only static linking is allowed, so no .so will be produced. linkstatic=False does not prevent static libraries from being created. The attribute is meant to control the creation of dynamic libraries.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line for this target, but not to its dependents.

Override the default dependency on malloc.

By default, C++ binaries are linked against //tools/cpp:malloc, which is an empty library so the binary ends up using libc malloc. This label must refer to a cc_library. If compilation is for a non-C++ rule, this option has no effect. The value of this attribute is ignored if linkshared=True is specified.

Remove matching options from the C++ compilation command. Subject to "Make" variable substitution. The value of this attribute is interpreted as a regular expression. Any preexisting COPTS that match this regular expression (including values explicitly specified in the rule's copts attribute) will be removed from COPTS for purposes of compiling this rule. This attribute should not be needed or used outside of third_party. The values are not preprocessed in any way other than the "Make" variable substitution.

The prefix to add to the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at is the value of this attribute prepended to their repository-relative path.

The prefix in the strip_include_prefix attribute is removed before this prefix is added.

The prefix to strip from the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at their path with this prefix cut off.

If it's a relative path, it's taken as a package-relative one. If it's an absolute one, it's understood as a repository-relative path.

The prefix in the include_prefix attribute is added after this prefix is stripped.

The list of header files published by this library to be textually included by sources in dependent rules.

This is the location for declaring header files that cannot be compiled on their own; that is, they always need to be textually included by other source files to build valid code.

A unique name for this target.

A single precompiled shared library. This ruleset will ensure it will be available to depending cc_hdrs_map targets.

Please DO NOT USE. This makes the SOL being propagated upwards to every dependee of this target.

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

Any additional files that you may want to pass to the linker, for example, linker scripts.
You have to separately pass any linker flags that the linker needs in order to be aware of this file.
You can do so via the linkopts attribute.

In contrast to rules_cc, the dynamic_deps of rules_cc_hdrs_map are simply translated into deps parameter,
and the providers (CcInfo vs CcSharedInfo) are used to steer the behavior further.

The list of other libraries that the library target depends on. Unlike with deps, the headers and include paths of these libraries (and all their transitive deps) are only used for compilation of this library, and not libraries that depend on it. Libraries specified with implementation_deps are still linked in binary targets that depend on this library.

Add these flags to the C++ linker command. Subject to "Make" variable substitution, Bourne shell tokenization and label expansion. Each string in this attribute is added to LINKOPTS before linking the binary target.
Each element of this list that does not start with $ or - is assumed to be the label of a target in deps. The list of files generated by that target is appended to the linker options. An error is reported if the label is invalid, or is not declared in deps.

The prefix to add to the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at is the value of this attribute prepended to their repository-relative path.

The prefix in the strip_include_prefix attribute is removed before this prefix is added.

The prefix to strip from the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at their path with this prefix cut off.

If it's a relative path, it's taken as a package-relative one. If it's an absolute one, it's understood as a repository-relative path.

The prefix in the include_prefix attribute is added after this prefix is stripped.

A unique name for this target.

Specify the name of the created .a file (that is decoupled from the rule instance name).
Note, that the 'cc_archive' is opinionated and will remove any leading 'lib' prefix and any '.a' in the name
(meaning 'libTest.a.x64.a' will become 'Test.x64' and will produce 'libTest.x64.a')

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

The list of source files.

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

List of headers that CANNOT be included by dependent rules.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

The list of files that are regarded as C++20 Modules Interface.

C++ Standard has no restriction about module interface file extension

• Clang use cppm
• GCC can use any source file extension
• MSVC use ixx

The use is guarded by the flag --experimental_cpp_modules.

The Windows DEF file to be passed to linker.

This attribute should only be used when Windows is the target platform. It can be used to export symbols during linking a shared library.

Any additional files you might want to pass to the compiler command line, such as sanitizer ignorelists, for example.
Files specified here can then be used in copts with the $(location) function.

Any additional files that you may want to pass to the linker, for example, linker scripts.
You have to separately pass any linker flags that the linker needs in order to be aware of this file.
You can do so via the linkopts attribute.

Add these options to the C compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.
Each string in this attribute is added in the given order to COPTS before compiling the binary target. The flags take effect only for compiling this target, not its dependencies, so be careful about header files included elsewhere. All paths should be relative to the workspace, not to the current package.

If the package declares the feature no_copts_tokenization, Bourne shell tokenization applies only to strings that consist of a single "Make" variable.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line to this target, as well as to every rule that depends on it. Be very careful, since this may have far-reaching effects. When in doubt, add define values to local_defines instead.

In contrast to rules_cc, the dynamic_deps of rules_cc_hdrs_map are simply translated into deps parameter,
and the providers (CcInfo vs CcSharedInfo) are used to steer the behavior further.

The list of other libraries that the library target depends on. Unlike with deps, the headers and include paths of these libraries (and all their transitive deps) are only used for compilation of this library, and not libraries that depend on it. Libraries specified with implementation_deps are still linked in binary targets that depend on this library.

List of include dirs to be added to the compile line.
Subject to "Make variable" substitution. Each string is prepended with -isystem and added to COPTS. Unlike COPTS, these flags are added for this rule and every rule that depends on it. (Note: not the rules it depends upon!) Be very careful, since this may have far-reaching effects. When in doubt, add "-I" flags to COPTS instead.

Headers must be added to srcs or hdrs, otherwise they will not be available to dependent rules when compilation is sandboxed (the default).

Add these flags to the C++ linker command. Subject to "Make" variable substitution, Bourne shell tokenization and label expansion. Each string in this attribute is added to LINKOPTS before linking the binary target.
Each element of this list that does not start with $ or - is assumed to be the label of a target in deps. The list of files generated by that target is appended to the linker options. An error is reported if the label is invalid, or is not declared in deps.

Create a shared library. To enable this attribute, include linkshared=True in your rule. By default this option is off.

Simultaneously compiles and links the specified C++ source file into the final binary. This trickery is required to introduce timestamp information into binaries; if we compiled the source file to an object file in the usual way, the timestamp would be incorrect. A linkstamp compilation may not include any particular set of compiler flags and so should not depend on any particular header, compiler option, or other build variable. This option should only be needed in the base package.

If enabled and this is a binary or test, this option tells the build tool to link in .a's instead of .so's for user libraries whenever possible. System libraries such as libc (but not the C/C++ runtime libraries, see below) are still linked dynamically, as are libraries for which there is no static library. So the resulting executable will still be dynamically linked, hence only mostly static.
The linkstatic attribute has a different meaning if used on a cc_library() rule. For a C++ library, linkstatic=True indicates that only static linking is allowed, so no .so will be produced. linkstatic=False does not prevent static libraries from being created. The attribute is meant to control the creation of dynamic libraries.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line for this target, but not to its dependents.

Remove matching options from the C++ compilation command. Subject to "Make" variable substitution. The value of this attribute is interpreted as a regular expression. Any preexisting COPTS that match this regular expression (including values explicitly specified in the rule's copts attribute) will be removed from COPTS for purposes of compiling this rule. This attribute should not be needed or used outside of third_party. The values are not preprocessed in any way other than the "Make" variable substitution.

The prefix to add to the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at is the value of this attribute prepended to their repository-relative path.

The prefix in the strip_include_prefix attribute is removed before this prefix is added.

The prefix to strip from the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at their path with this prefix cut off.

If it's a relative path, it's taken as a package-relative one. If it's an absolute one, it's understood as a repository-relative path.

The prefix in the include_prefix attribute is added after this prefix is stripped.

The list of header files published by this library to be textually included by sources in dependent rules.

This is the location for declaring header files that cannot be compiled on their own; that is, they always need to be textually included by other source files to build valid code.

A unique name for this target.

Whether to encode build information into the binary. Possible values:

• stamp = 1: Always stamp the build information into the binary, even in --nostamp builds. This setting should be avoided, since it potentially kills remote caching for the binary and any downstream actions that depend on it.

• stamp = 0: Always replace build information by constant values. This gives good build result caching.

• stamp = -1: Embedding of build information is controlled by the --[no]stamp flag.

Stamped binaries are not rebuilt unless their dependencies change.

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

The list of source files.

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

The list of files that are regarded as C++20 Modules Interface.

C++ Standard has no restriction about module interface file extension

• Clang use cppm
• GCC can use any source file extension
• MSVC use ixx

The use is guarded by the flag --experimental_cpp_modules.

The Windows DEF file to be passed to linker.

This attribute should only be used when Windows is the target platform. It can be used to export symbols during linking a shared library.

Any additional files you might want to pass to the compiler command line, such as sanitizer ignorelists, for example.
Files specified here can then be used in copts with the $(location) function.

Any additional files that you may want to pass to the linker, for example, linker scripts.
You have to separately pass any linker flags that the linker needs in order to be aware of this file.
You can do so via the linkopts attribute.

Add these options to the C compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.
Each string in this attribute is added in the given order to COPTS before compiling the binary target. The flags take effect only for compiling this target, not its dependencies, so be careful about header files included elsewhere. All paths should be relative to the workspace, not to the current package.

If the package declares the feature no_copts_tokenization, Bourne shell tokenization applies only to strings that consist of a single "Make" variable.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line to this target, as well as to every rule that depends on it. Be very careful, since this may have far-reaching effects. When in doubt, add define values to local_defines instead.

In contrast to rules_cc, the dynamic_deps of rules_cc_hdrs_map are simply translated into deps parameter,
and the providers (CcInfo vs CcSharedInfo) are used to steer the behavior further.

List of include dirs to be added to the compile line.
Subject to "Make variable" substitution. Each string is prepended with -isystem and added to COPTS. Unlike COPTS, these flags are added for this rule and every rule that depends on it. (Note: not the rules it depends upon!) Be very careful, since this may have far-reaching effects. When in doubt, add "-I" flags to COPTS instead.

Headers must be added to srcs or hdrs, otherwise they will not be available to dependent rules when compilation is sandboxed (the default).

Control linking of extra libraries.

By default, C++ binaries are linked against //tools/cpp:link_extra_lib, which by default depends on the label flag //tools/cpp:link_extra_libs. Without setting the flag, this library is empty by default. Setting the label flag allows linking optional dependencies, such as overrides for weak symbols, interceptors for shared library functions, or special runtime libraries (for malloc replacements, prefer malloc or --custom_malloc). Setting this attribute to None disables this behaviour.

Add these flags to the C++ linker command. Subject to "Make" variable substitution, Bourne shell tokenization and label expansion. Each string in this attribute is added to LINKOPTS before linking the binary target.
Each element of this list that does not start with $ or - is assumed to be the label of a target in deps. The list of files generated by that target is appended to the linker options. An error is reported if the label is invalid, or is not declared in deps.

Create a shared library. To enable this attribute, include linkshared=True in your rule. By default this option is off.

If enabled and this is a binary or test, this option tells the build tool to link in .a's instead of .so's for user libraries whenever possible. System libraries such as libc (but not the C/C++ runtime libraries, see below) are still linked dynamically, as are libraries for which there is no static library. So the resulting executable will still be dynamically linked, hence only mostly static.
The linkstatic attribute has a different meaning if used on a cc_library() rule. For a C++ library, linkstatic=True indicates that only static linking is allowed, so no .so will be produced. linkstatic=False does not prevent static libraries from being created. The attribute is meant to control the creation of dynamic libraries.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line for this target, but not to its dependents.

Override the default dependency on malloc.

By default, C++ binaries are linked against //tools/cpp:malloc, which is an empty library so the binary ends up using libc malloc. This label must refer to a cc_library. If compilation is for a non-C++ rule, this option has no effect. The value of this attribute is ignored if linkshared=True is specified.

Remove matching options from the C++ compilation command. Subject to "Make" variable substitution. The value of this attribute is interpreted as a regular expression. Any preexisting COPTS that match this regular expression (including values explicitly specified in the rule's copts attribute) will be removed from COPTS for purposes of compiling this rule. This attribute should not be needed or used outside of third_party. The values are not preprocessed in any way other than the "Make" variable substitution.

A unique name for this target.

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

List of headers that CANNOT be included by dependent rules.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

The list of files that are regarded as C++20 Modules Interface.

C++ Standard has no restriction about module interface file extension

• Clang use cppm
• GCC can use any source file extension
• MSVC use ixx

The use is guarded by the flag --experimental_cpp_modules.

The Windows DEF file to be passed to linker.

This attribute should only be used when Windows is the target platform. It can be used to export symbols during linking a shared library.

A unique name for this target.

If 1, any binary that depends (directly or indirectly) on this C++ precompiled library will link in all the object files archived in the static library, even if some contain no symbols referenced by the binary. This is useful if your code isn't explicitly called by code in the binary, e.g., if your code registers to receive some callback provided by some service.

This attribute contains a list of targets that are claimed to be exported by the current shared library.

Any target deps is already understood to be exported by the shared library. This attribute should be used to list any targets that are exported by the shared library but are transitive dependencies of deps.

Note that this attribute is not actually adding a dependency edge to those targets, the dependency edge should instead be created by deps.The entries in this attribute are just strings. Keep in mind that when placing a target in this attribute, this is considered a claim that the shared library exports the symbols from that target. The cc_shared_library logic doesn't actually handle telling the linker which symbols should be exported.

The following syntax is allowed:

//foo:pkg to account for any target in foo/BUILD

//foo:subpackages to account for any target in foo/BUILD or any other package below foo/ like foo/bar/BUILD

(Not yet implemented)

Specify the name of the created SOL file (that is decoupled from the rule instance name).
Note, that the 'cc_so' is opinionated and will remove any leading 'lib' prefix and any '.so' in the name
(meaning 'libTest.so.x64.so' will become 'Test.x64' and will produce 'libTest.x64.so')

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

The list of source files.

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

List of headers that CANNOT be included by dependent rules.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

The list of files that are regarded as C++20 Modules Interface.

C++ Standard has no restriction about module interface file extension

• Clang use cppm
• GCC can use any source file extension
• MSVC use ixx

The use is guarded by the flag --experimental_cpp_modules.

The Windows DEF file to be passed to linker.

This attribute should only be used when Windows is the target platform. It can be used to export symbols during linking a shared library.

Any additional files you might want to pass to the compiler command line, such as sanitizer ignorelists, for example.
Files specified here can then be used in copts with the $(location) function.

Any additional files that you may want to pass to the linker, for example, linker scripts.
You have to separately pass any linker flags that the linker needs in order to be aware of this file.
You can do so via the linkopts attribute.

Add these options to the C compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.
Each string in this attribute is added in the given order to COPTS before compiling the binary target. The flags take effect only for compiling this target, not its dependencies, so be careful about header files included elsewhere. All paths should be relative to the workspace, not to the current package.

If the package declares the feature no_copts_tokenization, Bourne shell tokenization applies only to strings that consist of a single "Make" variable.

Add these options to the C++ compilation command. Subject to "Make variable" substitution and Bourne shell tokenization.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line to this target, as well as to every rule that depends on it. Be very careful, since this may have far-reaching effects. When in doubt, add define values to local_defines instead.

In contrast to rules_cc, the dynamic_deps of rules_cc_hdrs_map are simply translated into deps parameter,
and the providers (CcInfo vs CcSharedInfo) are used to steer the behavior further.

The list of other libraries that the library target depends on. Unlike with deps, the headers and include paths of these libraries (and all their transitive deps) are only used for compilation of this library, and not libraries that depend on it. Libraries specified with implementation_deps are still linked in binary targets that depend on this library.

List of include dirs to be added to the compile line.
Subject to "Make variable" substitution. Each string is prepended with -isystem and added to COPTS. Unlike COPTS, these flags are added for this rule and every rule that depends on it. (Note: not the rules it depends upon!) Be very careful, since this may have far-reaching effects. When in doubt, add "-I" flags to COPTS instead.

Headers must be added to srcs or hdrs, otherwise they will not be available to dependent rules when compilation is sandboxed (the default).

Control linking of extra libraries.

By default, C++ binaries are linked against //tools/cpp:link_extra_lib, which by default depends on the label flag //tools/cpp:link_extra_libs. Without setting the flag, this library is empty by default. Setting the label flag allows linking optional dependencies, such as overrides for weak symbols, interceptors for shared library functions, or special runtime libraries (for malloc replacements, prefer malloc or --custom_malloc). Setting this attribute to None disables this behaviour.

Add these flags to the C++ linker command. Subject to "Make" variable substitution, Bourne shell tokenization and label expansion. Each string in this attribute is added to LINKOPTS before linking the binary target.
Each element of this list that does not start with $ or - is assumed to be the label of a target in deps. The list of files generated by that target is appended to the linker options. An error is reported if the label is invalid, or is not declared in deps.

Create a shared library. To enable this attribute, include linkshared=True in your rule. By default this option is off.

Simultaneously compiles and links the specified C++ source file into the final binary. This trickery is required to introduce timestamp information into binaries; if we compiled the source file to an object file in the usual way, the timestamp would be incorrect. A linkstamp compilation may not include any particular set of compiler flags and so should not depend on any particular header, compiler option, or other build variable. This option should only be needed in the base package.

If enabled and this is a binary or test, this option tells the build tool to link in .a's instead of .so's for user libraries whenever possible. System libraries such as libc (but not the C/C++ runtime libraries, see below) are still linked dynamically, as are libraries for which there is no static library. So the resulting executable will still be dynamically linked, hence only mostly static.
The linkstatic attribute has a different meaning if used on a cc_library() rule. For a C++ library, linkstatic=True indicates that only static linking is allowed, so no .so will be produced. linkstatic=False does not prevent static libraries from being created. The attribute is meant to control the creation of dynamic libraries.

List of defines to add to the compile line. Subject to "Make" variable substitution and Bourne shell tokenization. Each string, which must consist of a single Bourne shell token, is prepended with -D and added to the compile command line for this target, but not to its dependents.

Override the default dependency on malloc.

By default, C++ binaries are linked against //tools/cpp:malloc, which is an empty library so the binary ends up using libc malloc. This label must refer to a cc_library. If compilation is for a non-C++ rule, this option has no effect. The value of this attribute is ignored if linkshared=True is specified.

Remove matching options from the C++ compilation command. Subject to "Make" variable substitution. The value of this attribute is interpreted as a regular expression. Any preexisting COPTS that match this regular expression (including values explicitly specified in the rule's copts attribute) will be removed from COPTS for purposes of compiling this rule. This attribute should not be needed or used outside of third_party. The values are not preprocessed in any way other than the "Make" variable substitution.

The prefix to add to the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at is the value of this attribute prepended to their repository-relative path.

The prefix in the strip_include_prefix attribute is removed before this prefix is added.

The prefix to strip from the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at their path with this prefix cut off.

If it's a relative path, it's taken as a package-relative one. If it's an absolute one, it's understood as a repository-relative path.

The prefix in the include_prefix attribute is added after this prefix is stripped.

The list of header files published by this library to be textually included by sources in dependent rules.

This is the location for declaring header files that cannot be compiled on their own; that is, they always need to be textually included by other source files to build valid code.

A unique name for this target.

A single precompiled shared library. This ruleset will ensure it will be available to depending cc_hdrs_map targets.

Please DO NOT USE. This makes the SOL being propagated upwards to every dependee of this target.

The list of files needed by this target at runtime. See general comments about data at Typical attributes defined by most build rules.

The list of dependencies of current target

List of headers that may be included by dependent rules transitively.
Notice: the cutoff happens during compilation.

Dictionary describing paths under which header files should be avaiable as.

Keys are simple glob pathnames, used to match agains all header files avaiable in the rule.
Values are list of paths to which matching header files should be mapped.

'{filename}' is special token used to signify to matching file name.

For example:
'"**/*o.hpp": ["a/{filename}"]' - will ensure all hpp files with names ending with '0'
will be also avaible as if they were placed in a subdirectory.

Any additional files that you may want to pass to the linker, for example, linker scripts.
You have to separately pass any linker flags that the linker needs in order to be aware of this file.
You can do so via the linkopts attribute.

In contrast to rules_cc, the dynamic_deps of rules_cc_hdrs_map are simply translated into deps parameter,
and the providers (CcInfo vs CcSharedInfo) are used to steer the behavior further.

The list of other libraries that the library target depends on. Unlike with deps, the headers and include paths of these libraries (and all their transitive deps) are only used for compilation of this library, and not libraries that depend on it. Libraries specified with implementation_deps are still linked in binary targets that depend on this library.

Add these flags to the C++ linker command. Subject to "Make" variable substitution, Bourne shell tokenization and label expansion. Each string in this attribute is added to LINKOPTS before linking the binary target.
Each element of this list that does not start with $ or - is assumed to be the label of a target in deps. The list of files generated by that target is appended to the linker options. An error is reported if the label is invalid, or is not declared in deps.

The prefix to add to the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at is the value of this attribute prepended to their repository-relative path.

The prefix in the strip_include_prefix attribute is removed before this prefix is added.

The prefix to strip from the paths of the headers of this rule.
When set, the headers in the hdrs attribute of this rule are accessible at their path with this prefix cut off.

If it's a relative path, it's taken as a package-relative one. If it's an absolute one, it's understood as a repository-relative path.

The prefix in the include_prefix attribute is added after this prefix is stripped.