deploy: e3003dd

main/flatten.html

@@ -603,7 +603,7 @@ <h2 id="rules_foreign_cc_dependencies"><a class="header" href="#rules_foreign_cc
 <tr><td align="left"><a id="rules_foreign_cc_dependencies-register_preinstalled_tools"></a>register_preinstalled_tools</td><td align="left">If true, toolchains will be registered for the native built tools installed on the exec host</td><td align="left"><code>True</code></td></tr>
 <tr><td align="left"><a id="rules_foreign_cc_dependencies-register_built_tools"></a>register_built_tools</td><td align="left">If true, toolchains that build the tools from source are registered</td><td align="left"><code>True</code></td></tr>
 <tr><td align="left"><a id="rules_foreign_cc_dependencies-register_toolchains"></a>register_toolchains</td><td align="left">If true, registers the toolchains via native.register_toolchains. Used by bzlmod</td><td align="left"><code>True</code></td></tr>
-<tr><td align="left"><a id="rules_foreign_cc_dependencies-register_built_pkgconfig_toolchain"></a>register_built_pkgconfig_toolchain</td><td align="left">If true, the built pkgconfig toolchain will be registered. On Windows it may be preferrable to set this to False, as this requires the --enable_runfiles bazel option. Also note that building pkgconfig from source under bazel results in paths that are more than 256 characters long, which will not work on Windows unless the following options are added to the .bazelrc and symlinks are enabled in Windows.<br><br>startup --windows_enable_symlinks -&gt; This is required to enable symlinking to avoid long runfile paths build --action_env=MSYS=winsymlinks:nativestrict -&gt; This is required to enable symlinking to avoid long runfile paths startup --output_user_root=C:/b  -&gt; This is required to keep paths as short as possible</td><td align="left"><code>False</code></td></tr>
+<tr><td align="left"><a id="rules_foreign_cc_dependencies-register_built_pkgconfig_toolchain"></a>register_built_pkgconfig_toolchain</td><td align="left">If true, the built pkgconfig toolchain will be registered. On Windows it may be preferrable to set this to False, as this requires the --enable_runfiles bazel option. Also note that building pkgconfig from source under bazel results in paths that are more than 256 characters long, which will not work on Windows unless the following options are added to the .bazelrc and symlinks are enabled in Windows.<br><br>startup --windows_enable_symlinks -&gt; This is required to enable symlinking to avoid long runfile paths build --action_env=MSYS=winsymlinks:nativestrict -&gt; This is required to enable symlinking to avoid long runfile paths startup --output_user_root=C:/b  -&gt; This is required to keep paths as short as possible</td><td align="left"><code>True</code></td></tr>
 </tbody></table>
 
                     </main>

main/index.html

@@ -149,7 +149,7 @@ <h1 class="menu-title">Rules ForeignCc</h1>
                         <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/bac2c19d2352eb4e984a09c113703cc4840c5bbd">bac2c19</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/e3003dd17f0f06df912f9a43aff51f3024c11679">e3003dd</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 @@ <h2 id="setup"><a class="header" href="#setup">Setup</a></h2>
     #       release on the releases page: https://github.com/bazelbuild/rules_foreign_cc/releases
     #
     # sha256 = &quot;...&quot;,
-    strip_prefix = &quot;rules_foreign_cc-bac2c19d2352eb4e984a09c113703cc4840c5bbd&quot;,
-    url = &quot;https://github.com/bazelbuild/rules_foreign_cc/archive/bac2c19d2352eb4e984a09c113703cc4840c5bbd.tar.gz&quot;,
+    strip_prefix = &quot;rules_foreign_cc-e3003dd17f0f06df912f9a43aff51f3024c11679&quot;,
+    url = &quot;https://github.com/bazelbuild/rules_foreign_cc/archive/e3003dd17f0f06df912f9a43aff51f3024c11679.tar.gz&quot;,
 )
 
 load(&quot;@rules_foreign_cc//foreign_cc:repositories.bzl&quot;, &quot;rules_foreign_cc_dependencies&quot;)

main/print.html

@@ -150,7 +150,7 @@ <h1 class="menu-title">Rules ForeignCc</h1>
                         <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/bac2c19d2352eb4e984a09c113703cc4840c5bbd">bac2c19</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/e3003dd17f0f06df912f9a43aff51f3024c11679">e3003dd</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 @@ <h2 id="setup"><a class="header" href="#setup">Setup</a></h2>
     #       release on the releases page: https://github.com/bazelbuild/rules_foreign_cc/releases
     #
     # sha256 = &quot;...&quot;,
-    strip_prefix = &quot;rules_foreign_cc-bac2c19d2352eb4e984a09c113703cc4840c5bbd&quot;,
-    url = &quot;https://github.com/bazelbuild/rules_foreign_cc/archive/bac2c19d2352eb4e984a09c113703cc4840c5bbd.tar.gz&quot;,
+    strip_prefix = &quot;rules_foreign_cc-e3003dd17f0f06df912f9a43aff51f3024c11679&quot;,
+    url = &quot;https://github.com/bazelbuild/rules_foreign_cc/archive/e3003dd17f0f06df912f9a43aff51f3024c11679.tar.gz&quot;,
 )
 
 load(&quot;@rules_foreign_cc//foreign_cc:repositories.bzl&quot;, &quot;rules_foreign_cc_dependencies&quot;)
@@ -989,7 +989,7 @@ <h2 id="rules_foreign_cc_dependencies"><a class="header" href="#rules_foreign_cc
 <tr><td align="left"><a id="rules_foreign_cc_dependencies-register_preinstalled_tools"></a>register_preinstalled_tools</td><td align="left">If true, toolchains will be registered for the native built tools installed on the exec host</td><td align="left"><code>True</code></td></tr>
 <tr><td align="left"><a id="rules_foreign_cc_dependencies-register_built_tools"></a>register_built_tools</td><td align="left">If true, toolchains that build the tools from source are registered</td><td align="left"><code>True</code></td></tr>
 <tr><td align="left"><a id="rules_foreign_cc_dependencies-register_toolchains"></a>register_toolchains</td><td align="left">If true, registers the toolchains via native.register_toolchains. Used by bzlmod</td><td align="left"><code>True</code></td></tr>
-<tr><td align="left"><a id="rules_foreign_cc_dependencies-register_built_pkgconfig_toolchain"></a>register_built_pkgconfig_toolchain</td><td align="left">If true, the built pkgconfig toolchain will be registered. On Windows it may be preferrable to set this to False, as this requires the --enable_runfiles bazel option. Also note that building pkgconfig from source under bazel results in paths that are more than 256 characters long, which will not work on Windows unless the following options are added to the .bazelrc and symlinks are enabled in Windows.<br><br>startup --windows_enable_symlinks -&gt; This is required to enable symlinking to avoid long runfile paths build --action_env=MSYS=winsymlinks:nativestrict -&gt; This is required to enable symlinking to avoid long runfile paths startup --output_user_root=C:/b  -&gt; This is required to keep paths as short as possible</td><td align="left"><code>False</code></td></tr>
+<tr><td align="left"><a id="rules_foreign_cc_dependencies-register_built_pkgconfig_toolchain"></a>register_built_pkgconfig_toolchain</td><td align="left">If true, the built pkgconfig toolchain will be registered. On Windows it may be preferrable to set this to False, as this requires the --enable_runfiles bazel option. Also note that building pkgconfig from source under bazel results in paths that are more than 256 characters long, which will not work on Windows unless the following options are added to the .bazelrc and symlinks are enabled in Windows.<br><br>startup --windows_enable_symlinks -&gt; This is required to enable symlinking to avoid long runfile paths build --action_env=MSYS=winsymlinks:nativestrict -&gt; This is required to enable symlinking to avoid long runfile paths startup --output_user_root=C:/b  -&gt; This is required to keep paths as short as possible</td><td align="left"><code>True</code></td></tr>
 </tbody></table>
 
                     </main>