A repository of pacman packages for use with the new rtools 4.0 build system. Successful builds from the master branch of this repository are automatically deployed on bintray and become eventually available via pacman in Rtools 4.0.

To build a mingw-w64 package, open an rtools40 shell, cd into the package directory and run makepkg-mingw like this:

cd rtools-packages/mingw-w64-arrow
makepkg-mingw --syncdeps

The --syncdeps flag will automatically install package dependencies (see the next section if you need additional non-rtools build tools). Add --noconfirm to the command to skip the interactive confirmation prompt.

This will first build the 64-bit package mingw-w64-x86_64-arrow, and after that start the entire process from scratch to build the 32-bit package mingw-w64-i686-arrow. If you only want to build for a single architecture you can control this with the MINGW_INSTALLS environment variable.

Upcon successful completion it generates binary packages for 32 and 64 bit mingw-w64, for example: mingw-w64-i686-arrow-0.17.0-any.pkg.tar.xz and mingw-w64-x86_64-arrow-0.17.0-any.pkg.tar.xz. You can install these with pacman -U (U for upgrade):

pacman -U mingw-w64-i686-arrow-0.17.0-any.pkg.tar.xz
pacman -U mingw-w64-x86_64-arrow-0.17.0-any.pkg.tar.xz

Once the system library has been installed with pacman, you can link to it in your R package in the usual way. The rtools40 compiler will automatically find the headers and libraries for installed system libraries, just like on Linux.

To add or update a pacman package in rtools40, please send a pull request to the rtools-packages repository. The CI will automatically build it for you, but please test locally before sending the pull request.

If you want to add a new rtools40 package that is already available in msys2, you can simply adapt the PKGUILD from the their msys2/MINGW-packages repositories. However there is one important thing that needs to be changed for use with R:

You need to adapt the build scripts in the PKGBUILD to only build static libraries (libfoo.a files). For example with autotools you may need to add --enable-static --disable-shared and for cmake you may need something like -DBUILD_SHARED_LIBS=OFF. Some C/C++ libraries use custom build scripts, in which case you need to figure out how to make it produce static libraries.

This is important because Windows R binary packages need to be standalone and redistributable, so packages in the rtools-packages repo may not contain dll files.

Some C/C++ system libs need additional build utilities which we do not provide in rtools, such as autoconf. Build utilities are the pacman packages that are not prefixed with mingw-w64. You can get these from the upstream msys2 pacman repository. There many of them, and they change frequently. Build utilities should be declared in the makedepends of the PKGBUILD file. You should not use these utilities from within R packages, only for building pacman packages.

By default, the rtools40 environment is frozen in a stable state and only allows you to install extra rtools packages. Enabling the upstream msys2 repository and installing extra utilities may alter the rtools40 behavior, so avoid this on important R package build servers.

To enable the upstream msys repo, open the file c:\rtools40\etc\pacman.conf in a text editor and uncomment the following 2 lines at the very end of the file:

## 3rd party msys2 packages (rtools hackers only!)
[msys]
Include = /etc/pacman.d/mirrorlist.msys

Now update the runtime system: open the rtools40 shell and run pacman -Syu. In some cases, this may first upgrade msys-runtime or bash which you are currently using, which causes the terminal window to freeze after the upgrade. Don't worry, this is expected and happens only once. Close the window and restart the rtools40 shell, and run pacman -Syu again.

Once the msys repo is enabled, you can install extra tools needed to build libraries and other software. For example you can install autoconf or vim and so on:

pacman -S autoconf automake libtool
pacman -S vim

Rtools40 will never install anything outside of your rtools40 installation directory. So if you somehow messed up the installation beyond repair, simply reinstall rtools40 to start over.