deploy: 0ae6a6d75a
This commit is contained in:
UebelAndre
parent
dd5de36150
commit
d6ff4418f7
|
|
@ -277,7 +277,7 @@ cmake(<a href="#cmake-name">name</a>, <a href="#cmake-additional_inputs">additio
|
|||
<tr><td align="left"><a id="cmake-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="cmake-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="cmake-generate_args"></a>generate_args</td><td align="left">Arguments for CMake's generate command. Arguments should be passed as key/value pairs. eg: <code>["-G Ninja", "--debug-output", "-DFOO=bar"]</code>. Note that unless a generator (<code>-G</code>) argument is provided, the default generators are <a href="https://cmake.org/cmake/help/latest/generator/Unix%20Makefiles.html">Unix Makefiles</a> for Linux and MacOS and <a href="https://cmake.org/cmake/help/latest/generator/Ninja.html">Ninja</a> for Windows.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-generate_crosstool_file"></a>generate_crosstool_file</td><td align="left">When True, CMake crosstool file will be generated from the toolchain values, provided cache-entries and env_vars (some values will still be passed as <code>-Dkey=value</code> and environment variables). If <code>CMAKE_TOOLCHAIN_FILE</code> cache entry is passed, specified crosstool file will be used When using this option to cross-compile, it is required to specify <code>CMAKE_SYSTEM_NAME</code> in the cache_entries</td><td align="left">Boolean</td><td align="left">optional</td><td align="left">True</td></tr>
|
||||
<tr><td align="left"><a id="cmake-install"></a>install</td><td align="left">If True, the <code>cmake --install</code> comand will be performed after a build</td><td align="left">Boolean</td><td align="left">optional</td><td align="left">True</td></tr>
|
||||
|
|
|
|||
|
|
@ -184,7 +184,7 @@ configure_make(<a href="#configure_make-name">name</a>, <a href="#configure_make
|
|||
<tr><td align="left"><a id="configure_make-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-install_prefix"></a>install_prefix</td><td align="left">Install prefix, i.e. relative path to where to install the result of the build. Passed to the 'configure' script with --prefix flag.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
|
|
|
|||
|
|
@ -188,7 +188,7 @@ boost_build(<a href="#boost_build-name">name</a>, <a href="#boost_build-addition
|
|||
<tr><td align="left"><a id="boost_build-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="boost_build-linkopts"></a>linkopts</td><td align="left">Optional link options to be passed up to the dependencies of this library</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
|
|
@ -229,7 +229,7 @@ cmake(<a href="#cmake-name">name</a>, <a href="#cmake-additional_inputs">additio
|
|||
<tr><td align="left"><a id="cmake-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="cmake-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="cmake-generate_args"></a>generate_args</td><td align="left">Arguments for CMake's generate command. Arguments should be passed as key/value pairs. eg: <code>["-G Ninja", "--debug-output", "-DFOO=bar"]</code>. Note that unless a generator (<code>-G</code>) argument is provided, the default generators are <a href="https://cmake.org/cmake/help/latest/generator/Unix%20Makefiles.html">Unix Makefiles</a> for Linux and MacOS and <a href="https://cmake.org/cmake/help/latest/generator/Ninja.html">Ninja</a> for Windows.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-generate_crosstool_file"></a>generate_crosstool_file</td><td align="left">When True, CMake crosstool file will be generated from the toolchain values, provided cache-entries and env_vars (some values will still be passed as <code>-Dkey=value</code> and environment variables). If <code>CMAKE_TOOLCHAIN_FILE</code> cache entry is passed, specified crosstool file will be used When using this option to cross-compile, it is required to specify <code>CMAKE_SYSTEM_NAME</code> in the cache_entries</td><td align="left">Boolean</td><td align="left">optional</td><td align="left">True</td></tr>
|
||||
<tr><td align="left"><a id="cmake-install"></a>install</td><td align="left">If True, the <code>cmake --install</code> comand will be performed after a build</td><td align="left">Boolean</td><td align="left">optional</td><td align="left">True</td></tr>
|
||||
|
|
@ -287,7 +287,7 @@ configure_make(<a href="#configure_make-name">name</a>, <a href="#configure_make
|
|||
<tr><td align="left"><a id="configure_make-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-install_prefix"></a>install_prefix</td><td align="left">Install prefix, i.e. relative path to where to install the result of the build. Passed to the 'configure' script with --prefix flag.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
|
|
@ -327,7 +327,7 @@ make(<a href="#make-name">name</a>, <a href="#make-additional_inputs">additional
|
|||
<tr><td align="left"><a id="make-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make-install_prefix"></a>install_prefix</td><td align="left">Install prefix, i.e. relative path to where to install the result of the build. Passed as an arg to "make" as PREFIX=<install_prefix>.</td><td align="left">String</td><td align="left">optional</td><td align="left">"$$INSTALLDIR$$"</td></tr>
|
||||
<tr><td align="left"><a id="make-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="make-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
|
|
@ -355,7 +355,7 @@ make_tool(<a href="#make_tool-name">name</a>, <a href="#make_tool-env">env</a>,
|
|||
<p><strong>ATTRIBUTES</strong></p>
|
||||
<table><thead><tr><th align="left">Name</th><th align="left">Description</th><th align="left">Type</th><th align="left">Mandatory</th><th align="left">Default</th></tr></thead><tbody>
|
||||
<tr><td align="left"><a id="make_tool-name"></a>name</td><td align="left">A unique name for this target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#name">Name</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="make_tool-env"></a>env</td><td align="left">Environment variables to set during the build.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make_tool-env"></a>env</td><td align="left">Environment variables to set during the build. This attribute is subject to make variable substitution.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make_tool-srcs"></a>srcs</td><td align="left">The target containing the build tool's sources</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
</tbody></table>
|
||||
<p><a id="#native_tool_toolchain"></a></p>
|
||||
|
|
@ -392,7 +392,7 @@ ninja(<a href="#ninja-name">name</a>, <a href="#ninja-additional_inputs">additio
|
|||
<tr><td align="left"><a id="ninja-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="ninja-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="ninja-directory"></a>directory</td><td align="left">A directory to pass as the <code>-C</code> argument. The rule will always use the root directory of the <code>lib_sources</code> attribute if this attribute is not set</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="ninja-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="ninja-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="ninja-linkopts"></a>linkopts</td><td align="left">Optional link options to be passed up to the dependencies of this library</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
|
|
@ -419,7 +419,7 @@ ninja_tool(<a href="#ninja_tool-name">name</a>, <a href="#ninja_tool-env">env</a
|
|||
<p><strong>ATTRIBUTES</strong></p>
|
||||
<table><thead><tr><th align="left">Name</th><th align="left">Description</th><th align="left">Type</th><th align="left">Mandatory</th><th align="left">Default</th></tr></thead><tbody>
|
||||
<tr><td align="left"><a id="ninja_tool-name"></a>name</td><td align="left">A unique name for this target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#name">Name</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="ninja_tool-env"></a>env</td><td align="left">Environment variables to set during the build.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja_tool-env"></a>env</td><td align="left">Environment variables to set during the build. This attribute is subject to make variable substitution.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja_tool-srcs"></a>srcs</td><td align="left">The target containing the build tool's sources</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
</tbody></table>
|
||||
<p><a id="#ForeignCcArtifactInfo"></a></p>
|
||||
|
|
|
|||
|
|
@ -149,7 +149,7 @@
|
|||
<h1 id="rules-foreigncc"><a class="header" href="#rules-foreigncc">Rules ForeignCc</a></h1>
|
||||
<p>Rules for building C/C++ projects using foreign build systems (non Bazel) inside Bazel projects.</p>
|
||||
<table><thead><tr><th>Release</th><th>Commit</th><th>Status</th></tr></thead><tbody>
|
||||
<tr><td>main</td><td><a href="https://github.com/bazelbuild/rules_foreign_cc/commit/091dc5d381dc6314fa6ad4288c7657b4536364af">091dc5d</a></td><td><a href="https://buildkite.com/bazel/rules-foreign-cc/builds?branch=main"><img src="https://badge.buildkite.com/c28afbf846e2077715c753dda1f4b820cdcc46cc6cde16503c.svg?branch=main" alt="Build status" /></a></td></tr>
|
||||
<tr><td>main</td><td><a href="https://github.com/bazelbuild/rules_foreign_cc/commit/0ae6a6d75a4da61952e6aea031e3d6afac8757c8">0ae6a6d</a></td><td><a href="https://buildkite.com/bazel/rules-foreign-cc/builds?branch=main"><img src="https://badge.buildkite.com/c28afbf846e2077715c753dda1f4b820cdcc46cc6cde16503c.svg?branch=main" alt="Build status" /></a></td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="overview"><a class="header" href="#overview">Overview</a></h2>
|
||||
<p>Rules ForeignCc is designed to help users build projects that are not built by Bazel and also
|
||||
|
|
@ -167,8 +167,8 @@ http_archive(
|
|||
# release on the releases page: https://github.com/bazelbuild/rules_foreign_cc/releases
|
||||
#
|
||||
# sha256 = "...",
|
||||
strip_prefix = "rules_foreign_cc-091dc5d381dc6314fa6ad4288c7657b4536364af",
|
||||
url = "https://github.com/bazelbuild/rules_foreign_cc/archive/091dc5d381dc6314fa6ad4288c7657b4536364af.tar.gz",
|
||||
strip_prefix = "rules_foreign_cc-0ae6a6d75a4da61952e6aea031e3d6afac8757c8",
|
||||
url = "https://github.com/bazelbuild/rules_foreign_cc/archive/0ae6a6d75a4da61952e6aea031e3d6afac8757c8.tar.gz",
|
||||
)
|
||||
|
||||
load("@rules_foreign_cc//foreign_cc:repositories.bzl", "rules_foreign_cc_dependencies")
|
||||
|
|
|
|||
|
|
@ -169,7 +169,7 @@ make(<a href="#make-name">name</a>, <a href="#make-additional_inputs">additional
|
|||
<tr><td align="left"><a id="make-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make-install_prefix"></a>install_prefix</td><td align="left">Install prefix, i.e. relative path to where to install the result of the build. Passed as an arg to "make" as PREFIX=<install_prefix>.</td><td align="left">String</td><td align="left">optional</td><td align="left">"$$INSTALLDIR$$"</td></tr>
|
||||
<tr><td align="left"><a id="make-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="make-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
|
|
|
|||
|
|
@ -170,7 +170,7 @@ ninja(<a href="#ninja-name">name</a>, <a href="#ninja-additional_inputs">additio
|
|||
<tr><td align="left"><a id="ninja-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="ninja-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="ninja-directory"></a>directory</td><td align="left">A directory to pass as the <code>-C</code> argument. The rule will always use the root directory of the <code>lib_sources</code> attribute if this attribute is not set</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="ninja-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="ninja-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="ninja-linkopts"></a>linkopts</td><td align="left">Optional link options to be passed up to the dependencies of this library</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
|
|
|
|||
|
|
@ -150,7 +150,7 @@
|
|||
<h1 id="rules-foreigncc"><a class="header" href="#rules-foreigncc">Rules ForeignCc</a></h1>
|
||||
<p>Rules for building C/C++ projects using foreign build systems (non Bazel) inside Bazel projects.</p>
|
||||
<table><thead><tr><th>Release</th><th>Commit</th><th>Status</th></tr></thead><tbody>
|
||||
<tr><td>main</td><td><a href="https://github.com/bazelbuild/rules_foreign_cc/commit/091dc5d381dc6314fa6ad4288c7657b4536364af">091dc5d</a></td><td><a href="https://buildkite.com/bazel/rules-foreign-cc/builds?branch=main"><img src="https://badge.buildkite.com/c28afbf846e2077715c753dda1f4b820cdcc46cc6cde16503c.svg?branch=main" alt="Build status" /></a></td></tr>
|
||||
<tr><td>main</td><td><a href="https://github.com/bazelbuild/rules_foreign_cc/commit/0ae6a6d75a4da61952e6aea031e3d6afac8757c8">0ae6a6d</a></td><td><a href="https://buildkite.com/bazel/rules-foreign-cc/builds?branch=main"><img src="https://badge.buildkite.com/c28afbf846e2077715c753dda1f4b820cdcc46cc6cde16503c.svg?branch=main" alt="Build status" /></a></td></tr>
|
||||
</tbody></table>
|
||||
<h2 id="overview"><a class="header" href="#overview">Overview</a></h2>
|
||||
<p>Rules ForeignCc is designed to help users build projects that are not built by Bazel and also
|
||||
|
|
@ -168,8 +168,8 @@ http_archive(
|
|||
# release on the releases page: https://github.com/bazelbuild/rules_foreign_cc/releases
|
||||
#
|
||||
# sha256 = "...",
|
||||
strip_prefix = "rules_foreign_cc-091dc5d381dc6314fa6ad4288c7657b4536364af",
|
||||
url = "https://github.com/bazelbuild/rules_foreign_cc/archive/091dc5d381dc6314fa6ad4288c7657b4536364af.tar.gz",
|
||||
strip_prefix = "rules_foreign_cc-0ae6a6d75a4da61952e6aea031e3d6afac8757c8",
|
||||
url = "https://github.com/bazelbuild/rules_foreign_cc/archive/0ae6a6d75a4da61952e6aea031e3d6afac8757c8.tar.gz",
|
||||
)
|
||||
|
||||
load("@rules_foreign_cc//foreign_cc:repositories.bzl", "rules_foreign_cc_dependencies")
|
||||
|
|
@ -319,7 +319,7 @@ cmake(<a href="cmake.html#cmake-name">name</a>, <a href="cmake.html#cmake-additi
|
|||
<tr><td align="left"><a id="cmake-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="cmake-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="cmake-generate_args"></a>generate_args</td><td align="left">Arguments for CMake's generate command. Arguments should be passed as key/value pairs. eg: <code>["-G Ninja", "--debug-output", "-DFOO=bar"]</code>. Note that unless a generator (<code>-G</code>) argument is provided, the default generators are <a href="https://cmake.org/cmake/help/latest/generator/Unix%20Makefiles.html">Unix Makefiles</a> for Linux and MacOS and <a href="https://cmake.org/cmake/help/latest/generator/Ninja.html">Ninja</a> for Windows.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-generate_crosstool_file"></a>generate_crosstool_file</td><td align="left">When True, CMake crosstool file will be generated from the toolchain values, provided cache-entries and env_vars (some values will still be passed as <code>-Dkey=value</code> and environment variables). If <code>CMAKE_TOOLCHAIN_FILE</code> cache entry is passed, specified crosstool file will be used When using this option to cross-compile, it is required to specify <code>CMAKE_SYSTEM_NAME</code> in the cache_entries</td><td align="left">Boolean</td><td align="left">optional</td><td align="left">True</td></tr>
|
||||
<tr><td align="left"><a id="cmake-install"></a>install</td><td align="left">If True, the <code>cmake --install</code> comand will be performed after a build</td><td align="left">Boolean</td><td align="left">optional</td><td align="left">True</td></tr>
|
||||
|
|
@ -392,7 +392,7 @@ configure_make(<a href="configure_make.html#configure_make-name">name</a>, <a hr
|
|||
<tr><td align="left"><a id="configure_make-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-install_prefix"></a>install_prefix</td><td align="left">Install prefix, i.e. relative path to where to install the result of the build. Passed to the 'configure' script with --prefix flag.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
|
|
@ -446,7 +446,7 @@ make(<a href="make.html#make-name">name</a>, <a href="make.html#make-additional_
|
|||
<tr><td align="left"><a id="make-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make-install_prefix"></a>install_prefix</td><td align="left">Install prefix, i.e. relative path to where to install the result of the build. Passed as an arg to "make" as PREFIX=<install_prefix>.</td><td align="left">String</td><td align="left">optional</td><td align="left">"$$INSTALLDIR$$"</td></tr>
|
||||
<tr><td align="left"><a id="make-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="make-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
|
|
@ -501,7 +501,7 @@ ninja(<a href="ninja.html#ninja-name">name</a>, <a href="ninja.html#ninja-additi
|
|||
<tr><td align="left"><a id="ninja-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="ninja-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="ninja-directory"></a>directory</td><td align="left">A directory to pass as the <code>-C</code> argument. The rule will always use the root directory of the <code>lib_sources</code> attribute if this attribute is not set</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="ninja-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="ninja-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="ninja-linkopts"></a>linkopts</td><td align="left">Optional link options to be passed up to the dependencies of this library</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
|
|
@ -561,7 +561,7 @@ boost_build(<a href="flatten.html#boost_build-name">name</a>, <a href="flatten.h
|
|||
<tr><td align="left"><a id="boost_build-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="boost_build-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="boost_build-linkopts"></a>linkopts</td><td align="left">Optional link options to be passed up to the dependencies of this library</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
|
|
@ -602,7 +602,7 @@ cmake(<a href="flatten.html#cmake-name">name</a>, <a href="flatten.html#cmake-ad
|
|||
<tr><td align="left"><a id="cmake-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="cmake-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="cmake-generate_args"></a>generate_args</td><td align="left">Arguments for CMake's generate command. Arguments should be passed as key/value pairs. eg: <code>["-G Ninja", "--debug-output", "-DFOO=bar"]</code>. Note that unless a generator (<code>-G</code>) argument is provided, the default generators are <a href="https://cmake.org/cmake/help/latest/generator/Unix%20Makefiles.html">Unix Makefiles</a> for Linux and MacOS and <a href="https://cmake.org/cmake/help/latest/generator/Ninja.html">Ninja</a> for Windows.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="cmake-generate_crosstool_file"></a>generate_crosstool_file</td><td align="left">When True, CMake crosstool file will be generated from the toolchain values, provided cache-entries and env_vars (some values will still be passed as <code>-Dkey=value</code> and environment variables). If <code>CMAKE_TOOLCHAIN_FILE</code> cache entry is passed, specified crosstool file will be used When using this option to cross-compile, it is required to specify <code>CMAKE_SYSTEM_NAME</code> in the cache_entries</td><td align="left">Boolean</td><td align="left">optional</td><td align="left">True</td></tr>
|
||||
<tr><td align="left"><a id="cmake-install"></a>install</td><td align="left">If True, the <code>cmake --install</code> comand will be performed after a build</td><td align="left">Boolean</td><td align="left">optional</td><td align="left">True</td></tr>
|
||||
|
|
@ -660,7 +660,7 @@ configure_make(<a href="flatten.html#configure_make-name">name</a>, <a href="fla
|
|||
<tr><td align="left"><a id="configure_make-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-install_prefix"></a>install_prefix</td><td align="left">Install prefix, i.e. relative path to where to install the result of the build. Passed to the 'configure' script with --prefix flag.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="configure_make-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
|
|
@ -700,7 +700,7 @@ make(<a href="flatten.html#make-name">name</a>, <a href="flatten.html#make-addit
|
|||
<tr><td align="left"><a id="make-data"></a>data</td><td align="left">Files needed by this rule at runtime. May list file or rule targets. Generally allows any target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make-install_prefix"></a>install_prefix</td><td align="left">Install prefix, i.e. relative path to where to install the result of the build. Passed as an arg to "make" as PREFIX=<install_prefix>.</td><td align="left">String</td><td align="left">optional</td><td align="left">"$$INSTALLDIR$$"</td></tr>
|
||||
<tr><td align="left"><a id="make-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="make-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
|
|
@ -728,7 +728,7 @@ make_tool(<a href="flatten.html#make_tool-name">name</a>, <a href="flatten.html#
|
|||
<p><strong>ATTRIBUTES</strong></p>
|
||||
<table><thead><tr><th align="left">Name</th><th align="left">Description</th><th align="left">Type</th><th align="left">Mandatory</th><th align="left">Default</th></tr></thead><tbody>
|
||||
<tr><td align="left"><a id="make_tool-name"></a>name</td><td align="left">A unique name for this target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#name">Name</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="make_tool-env"></a>env</td><td align="left">Environment variables to set during the build.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make_tool-env"></a>env</td><td align="left">Environment variables to set during the build. This attribute is subject to make variable substitution.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="make_tool-srcs"></a>srcs</td><td align="left">The target containing the build tool's sources</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
</tbody></table>
|
||||
<p><a id="#native_tool_toolchain"></a></p>
|
||||
|
|
@ -765,7 +765,7 @@ ninja(<a href="flatten.html#ninja-name">name</a>, <a href="flatten.html#ninja-ad
|
|||
<tr><td align="left"><a id="ninja-defines"></a>defines</td><td align="left">Optional compilation definitions to be passed to the dependencies of this library. They are NOT passed to the compiler, you should duplicate them in the configuration options.</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="ninja-deps"></a>deps</td><td align="left">Optional dependencies to be copied into the directory structure. Typically those directly required for the external building of the library/binaries. (i.e. those that the external build system will be looking for and paths to which are provided by the calling rule)</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">List of labels</a></td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
<tr><td align="left"><a id="ninja-directory"></a>directory</td><td align="left">A directory to pass as the <code>-C</code> argument. The rule will always use the root directory of the <code>lib_sources</code> attribute if this attribute is not set</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="ninja-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja-env"></a>env</td><td align="left">Environment variables to set during the build. <code>$(execpath)</code> macros may be used to point at files which are listed as <code>data</code>, <code>deps</code>, or <code>build_data</code>, but unlike with other rules, these will be replaced with absolute paths to those files, because the build does not run in the exec root. This attribute is subject to make variable substitution. No other macros are supported.Variables containing <code>PATH</code> (e.g. <code>PATH</code>, <code>LD_LIBRARY_PATH</code>, <code>CPATH</code>) entries will be prepended to the existing variable.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja-lib_name"></a>lib_name</td><td align="left">Library name. Defines the name of the install directory and the name of the static library, if no output files parameters are defined (any of static_libraries, shared_libraries, interface_libraries, binaries_names) Optional. If not defined, defaults to the target's name.</td><td align="left">String</td><td align="left">optional</td><td align="left">""</td></tr>
|
||||
<tr><td align="left"><a id="ninja-lib_source"></a>lib_source</td><td align="left">Label with source code to build. Typically a filegroup for the source of remote repository. Mandatory.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="ninja-linkopts"></a>linkopts</td><td align="left">Optional link options to be passed up to the dependencies of this library</td><td align="left">List of strings</td><td align="left">optional</td><td align="left">[]</td></tr>
|
||||
|
|
@ -792,7 +792,7 @@ ninja_tool(<a href="flatten.html#ninja_tool-name">name</a>, <a href="flatten.htm
|
|||
<p><strong>ATTRIBUTES</strong></p>
|
||||
<table><thead><tr><th align="left">Name</th><th align="left">Description</th><th align="left">Type</th><th align="left">Mandatory</th><th align="left">Default</th></tr></thead><tbody>
|
||||
<tr><td align="left"><a id="ninja_tool-name"></a>name</td><td align="left">A unique name for this target.</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#name">Name</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
<tr><td align="left"><a id="ninja_tool-env"></a>env</td><td align="left">Environment variables to set during the build.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja_tool-env"></a>env</td><td align="left">Environment variables to set during the build. This attribute is subject to make variable substitution.</td><td align="left"><a href="https://bazel.build/docs/skylark/lib/dict.html">Dictionary: String -> String</a></td><td align="left">optional</td><td align="left">{}</td></tr>
|
||||
<tr><td align="left"><a id="ninja_tool-srcs"></a>srcs</td><td align="left">The target containing the build tool's sources</td><td align="left"><a href="https://bazel.build/docs/build-ref.html#labels">Label</a></td><td align="left">required</td><td align="left"></td></tr>
|
||||
</tbody></table>
|
||||
<p><a id="#ForeignCcArtifactInfo"></a></p>
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Loading…
Reference in New Issue