Deploying to gh-pages from @ 1ae810d 🚀

r-admin/Add-on-packages.html

@@ -393,7 +393,7 @@ <h3 class="subsection anchored" data-number="6.3.1" data-anchor-id="windows"><sp
 <p>[At present binary packages are not distributed for <code>aarch64</code> Windows, so most of this subsection only applies to <code>x86_64</code>.]</p>
 <p>On Windows <code>install.packages</code> can also install a binary package from a local <code>zip</code> file (or the URL of such a file) by setting argument <code>repos</code> to <code>NULL</code>. <code>Rgui.exe</code> has a menu <code>Packages</code> with a GUI interface to <code>install.packages</code>, <code>update.packages</code> and <code>library</code>.</p>
 <p>Windows binary packages for R were distributed as a single binary containing either or both architectures (32- and 64-bit). Prior to R 4.2.0, they might contain only the 32-bit architecture.</p>
-<p><code>R CMD INSTALL</code> works in Windows to install source packages. No additional tools are needed if the package does not contain compiled code, and <code>install.packages(type="source")</code> will work for such packages. Those with compiled code need the tools (see <a href="Installing-R-under-Windows.html#the-windows-toolset">The Windows toolset</a>). The tools are found automatically by R when installed by the toolset installer. See <a href="https://cran.r-project.org/bin/windows/base/howto-R-devel.html">Building R and packages</a> for more details.</p>
+<p><code>R CMD INSTALL</code> works in Windows to install source packages. No additional tools are needed if the package does not contain compiled code, and <code>install.packages(type="source")</code> will work for such packages. Those with compiled code need the tools (see <a href="Installing-R-under-Windows.html#the-windows-toolset">The Windows toolset</a>). The tools are found automatically by R when installed by the toolset installer. See <a href="https://cran.r-project.org/bin/windows/base/howto-%7BNo%20value%20for%20%60RWTVERSION'%7D.html">Building {No value for ‘RWTVERSION’} and packages on Windows</a> for more details.</p>
 <p>Occasional permission problems after unpacking source packages have been seen on some systems: these have been circumvented by setting the environment variable <code>R_INSTALL_TAR</code> to <code>tar.exe</code>.</p>
 <p>If you have only a source package that is known to work with current R and just want a binary Windows build of it, you could make use of the building service offered at <a href="https://win-builder.r-project.org/" class="uri">https://win-builder.r-project.org/</a>.</p>
 <p>For almost all packages <code>R CMD INSTALL</code> will attempt to install both 32- and 64-bit builds of a package if run from a 32/64-bit install of R (only 64-bit builds and installs are supported since R 4.2.0). It will report success if the installation of the architecture of the running <code>R</code> succeeded, whether or not the other architecture was successfully installed. The exceptions are packages with a non-empty <code>configure.win</code> script or which make use of <code>src/Makefile.win</code>. If <code>configure.win</code> does something appropriate to both architectures use<a href="#fn4" class="footnote-ref" id="fnref4" role="doc-noteref"><sup>4</sup></a> option <code>--force-biarch</code>: otherwise <code>R CMD INSTALL --merge-multiarch</code> can be applied to a source tarball to merge separate 32- and 64-bit installs. (This can only be applied to a tarball, and will only succeed if both installs succeed.)</p>

r-admin/Installing-R-under-Windows.html

@@ -345,7 +345,7 @@ <h2 class="section anchored" data-number="3.1" data-anchor-id="building-from-sou
 <p>It is possible to use other 64-bit toolchains (including ‘MSYS2’) with UCRT support to build R, but this manual only documents that used for recent binary distributions of R. When using other toolchains, makefiles of R and packages may need to be adapted.</p>
 <section id="the-windows-toolset" class="level3 subsection" data-number="3.1.1">
 <h3 class="subsection anchored" data-number="3.1.1" data-anchor-id="the-windows-toolset"><span class="header-section-number">3.1.1</span> The Windows toolset</h3>
-<p>The binary distribution of R is currently built with tools from <a href="https://CRAN.R-project.org/bin/windows/Rtools/rtools44/rtools.html">Rtools44 for Windows</a>. See <a href="https://CRAN.R-project.org/bin/windows/base/howto-R-devel.html">Building R and packages</a> for more details on how to use it.</p>
+<p>The binary distribution of R is currently built with tools from <a href="https://CRAN.R-project.org/bin/windows/Rtools/rtools44/rtools.html">Rtools44 for Windows</a>. See <a href="https://CRAN.R-project.org/bin/windows/base/howto-%7BNo%20value%20for%20%60RWTVERSION'%7D.html">Building {No value for ‘RWTVERSION’} and packages on Windows</a> for more details on how to use it.</p>
 <p>The toolset includes compilers (currently GCC version 13.2.0 with selected additional patches) and runtime libraries from <a href="http://mingw-w64.org/">the ‘MinGW-w64’ project</a> and a number of pre-compiled static libraries and headers used by R and R packages, compiled by <a href="https://mxe.cc/">‘MXE’</a> (M cross environment, with updates maintained by Tomas Kalibera). The toolset also includes build tools from the <a href="https://www.msys2.org/">the ‘MSYS2’ project</a>. Additional build tools packaged by ‘MSYS2’ may be installed via a package manager (<code>pacman</code>).</p>
 <p>There is also an experimental variant of Rtools44 with support for 64-bit ARM CPUs (aarch64) via LLVM 17 toolchain using <code>clang</code>/<code>flang-new</code> compilers, <code>lld</code> linker, and libc++.</p>
 <p>The toolsets used for 64-bit Windows from 2008 to 2022 were based on MinGW-w64. The assistance of Yu Gong at a crucial step in porting R to MinGW-w64 is gratefully acknowledged, as well as help from Kai Tietz, the lead developer of the MinGW-w64 project and from Martin Storsjo.</p>