For the easiest installation, go to “Installing the CRAN package”.
If you experience any issues with that, try “Installing from Source with CMake”. This can produce a more efficient version of the library on Windows systems with Visual Studio.
To build a GPU-enabled version of the package, follow the steps in “Installing a GPU-enabled Build”.
If any of the above options do not work for you or do not meet your needs, please let the maintainers know by opening an issue.
When your package installation is done, you can check quickly if your LightGBM R-package is working by running the following:
install.packages("lightgbm", repos = "https://cran.r-project.org")
This is the easiest way to install lightgbm. It does not require
Visual Studio, and should work well on many different operating systems and compilers.
Each CRAN package is also available on LightGBM releases, with a name like
The steps above should work on most systems, but users with highly-customized environments might want to change how R builds packages from source.
To change the compiler used when installing the CRAN package, you can create a file
~/.R/Makevars which overrides
C compiler) and
For example, to use
gcc instead of
clang on Mac, you could use something like the following:
# ~/.R/Makevars CC=gcc-8 CXX=g++-8 CXX11=g++-8
You need to install git and CMake first.
Note: this method is only supported on 64-bit systems. If you need to run LightGBM on 32-bit Windows (i386), follow the instructions in “Installing the CRAN Package”.
NOTE: Windows users may need to run with administrator rights (either R or the command prompt, depending on the way you are installing this package).
Installing a 64-bit version of Rtools is mandatory.
CMake, be sure the following paths are added to the environment variable
PATH. These may have been automatically added when installing other software.
Rtools paths are required from
Rtools 4.0 onwards because paths and the list of included software was changed in
A “toolchain” refers to the collection of software used to build the library. The R package can be built with three different toolchains.
Warning for Windows users: it is recommended to use Visual Studio for its better multi-threading efficiency in Windows for many core systems. For very simple systems (dual core computers or worse), MinGW64 is recommended for maximum performance. If you do not know what to choose, it is recommended to use Visual Studio, the default compiler. Do not try using MinGW in Windows on many core systems. It may result in 10x slower results than Visual Studio.
Visual Studio (default)
By default, the package will be built with Visual Studio Build Tools.
MinGW (R 3.x)
If you are using R 3.x and installation fails with Visual Studio,
LightGBM will fall back to using MinGW bundled with
If you want to force
LightGBM to use MinGW (for any R version), pass
--use-mingw to the installation script.
Rscript build_r.R --use-mingw
MSYS2 (R 4.x)
If you are using R 4.x and installation fails with Visual Studio,
LightGBM will fall back to using MSYS2. This should work with the tools already bundled in
If you want to force
LightGBM to use MSYS2 (for any R version), pass
--use-msys2 to the installation script.
Rscript build_r.R --use-msys2
You can perform installation either with Apple Clang or gcc. In case you prefer Apple Clang, you should install OpenMP (details for installation can be found in Installation Guide) first and CMake version 3.16 or higher is required. In case you prefer gcc, you need to install it (details for installation can be found in Installation Guide) and set some environment variables to tell R to use
g++. If you install these from Homebrew, your versions of
gcc are most likely in
/usr/local/bin, as shown below.
# replace 8 with version of gcc installed on your machine export CXX=/usr/local/bin/g++-8 CC=/usr/local/bin/gcc-8
After following the “preparation” steps above for your operating system, build and install the R-package with the following commands:
git clone --recursive https://github.com/microsoft/LightGBM cd LightGBM Rscript build_r.R
build_r.R script builds the package in a temporary directory called
lightgbm_r. It will destroy and recreate that directory each time you run the script. That script supports the following command-line options:
--skip-install: Build the package tarball, but do not install it.
--use-gpu: Build a GPU-enabled version of the library.
--use-mingw: Force the use of MinGW toolchain, regardless of R version.
--use-msys2: Force the use of MSYS2 toolchain, regardless of R version.
Note: for the build with Visual Studio/VS Build Tools in Windows, you should use the Windows CMD or PowerShell.
You will need to install Boost and OpenCL first: details for installation can be found in Installation-Guide.
After installing these other libraries, follow the steps in “Installing from Source with CMake”. When you reach the step that mentions
build_r.R, pass the flag
Rscript build_r.R --use-gpu
Precompiled binaries for Mac and Windows are prepared by CRAN a few days after each release to CRAN. They can be installed with the following R code.
install.packages( "lightgbm" , type = "both" , repos = "https://cran.r-project.org" )
These packages do not require compilation, so they will be faster and easier to install than packages that are built from source.
CRAN does not prepare precompiled binaries for Linux, and as of this writing neither does this project.
Previous versions of LightGBM offered the ability to first compile the C++ library (
lib_lightgbm.dll) and then build an R package that wraps it.
As of version 3.0.0, this is no longer supported. If building from source is difficult for you, please open an issue.
Please visit demo:
The R package’s unit tests are run automatically on every commit, via integrations like Travis CI and Azure DevOps. Adding new tests in
R-package/tests/testthat is a valuable way to improve the reliability of the R package.
When adding tests, you may want to use test coverage to identify untested areas and to check if the tests you’ve added are covering all branches of the intended code.
The example below shows how to generate code coverage for the R package on a macOS or Linux setup, using
gcc-8 to compile
LightGBM. To adjust for your environment, swap out the ‘Install’ step with the relevant code from the instructions above.
# Install export CXX=/usr/local/bin/g++-8 export CC=/usr/local/bin/gcc-8 Rscript build_r.R --skip-install # Get coverage Rscript -e " \ coverage <- covr::package_coverage('./lightgbm_r', quiet=FALSE); print(coverage); covr::report(coverage, file = file.path(getwd(), 'coverage.html'), browse = TRUE); "
This section is primarily for maintainers, but may help users and contributors to understand the structure of the R package.
CMake to handle tasks like setting compiler and linker flags, including header file locations, and linking to other libraries. Because CRAN packages typically do not assume the presence of
CMake, the R package uses an alternative method that is in the CRAN-supported toolchain for building R packages with C++ code:
For more information on this approach, see “Writing R Extensions”.
From the root of the repository, run the following.
This will create a file
VERSION is the version of
Alternatively, GitHub Actions can generate this file for you. On a pull request, go to the “Files changed” tab and create a comment with this phrase:
/gha build r-artifacts
Go to https://github.com/microsoft/LightGBM/actions, and find the most recent run of the “R artifact builds” workflow. If it ran successfully, you’ll find a download link for the package (in
.zip format) in that run’s “Artifacts” section.
After building the package, install it with a command like the following:
R CMD install lightgbm_*.tar.gz
A lot of details are handled automatically by
R CMD build and
R CMD install, so it can be difficult to understand how the files in the R package are related to each other. An extensive treatment of those details is available in “Writing R Extensions”.
This section briefly explains the key files for building a CRAN package. To update the package, edit the files relevant to your change and re-run the steps in Build a CRAN Package.
Linux or Mac
At build time,
configure will be run and used to create a file
Makevars.in as a template.
autoconf. Do not edit it by hand. This file must be generated on Ubuntu 18.04.
If you have an Ubuntu 18.04 environment available, run the provided script from the root of the
If you do not have easy access to an Ubuntu 18.04 environment, the
configure script can be generated using Docker by running the code below from the root of this repo.
docker run \ -v $(pwd):/opt/LightGBM \ -t ubuntu:18.04 \ /bin/bash -c "cd /opt/LightGBM && ./R-package/recreate-configure.sh"
The version of
autoconf used by this project is stored in
R-package/AUTOCONF_UBUNTU_VERSION. To update that version, update that file and run the commands above. To see available versions, see https://packages.ubuntu.com/search?keywords=autoconf.
Configuring for Windows
At build time,
configure.win will be run and used to create a file
Makevars.win.in as a template.
lightgbm is tested automatically on every commit, across many combinations of operating system, R version, and compiler. This section describes how to test the package locally while you are developing.
All packages uploaded to CRAN must pass
R CMD check on Solaris 10. To test LightGBM on this operating system, you can use the free service R Hub, a free service generously provided by the R Consortium.
package_tarball <- paste0("lightgbm_", readLines("VERSION.txt"), ".tar.gz") rhub::check( path = package_tarball , email = "your_email_here" , check_args = "--as-cran" , platform = c( "solaris-x86-patched" , "solaris-x86-patched-ods" ) , env_vars = c( "R_COMPILE_AND_INSTALL_PACKAGES" = "always" ) )
All packages uploaded to CRAN must pass a build using
gcc instrumented with two sanitizers: the Address Sanitizer (ASAN) and the Undefined Behavior Sanitizer (UBSAN). For more background, see this blog post.
You can replicate these checks locally using Docker.
docker run \ -v $(pwd):/opt/LightGBM \ -it rhub/rocker-gcc-san \ /bin/bash cd /opt/LightGBM Rscript -e "install.packages(c('R6', 'data.table', 'jsonlite', 'testthat'), repos = 'https://cran.rstudio.com')" sh build-cran-package.sh Rdevel CMD install lightgbm_*.tar.gz cd R-package/tests Rscriptdevel testthat.R
All packages uploaded to CRAN must be built and tested without raising any issues from
valgrind is a profiler that can catch serious issues like memory leaks and illegal writes. For more information, see this blog post.
You can replicate these checks locally using Docker. Note that instrumented versions of R built to use
valgrind run much slower, and these tests may take as long as 20 minutes to run.
docker run \ -v $(pwd):/opt/LightGBM \ -it \ wch1/r-debug cd /opt/LightGBM RDscriptvalgrind -e "install.packages(c('R6', 'data.table', 'jsonlite', 'testthat'), repos = 'https://cran.rstudio.com')" sh build-cran-package.sh RDvalgrind CMD INSTALL \ --preclean \ --install-tests \ lightgbm_*.tar.gz cd R-package/tests RDvalgrind \ --no-readline \ --vanilla \ -d "valgrind --tool=memcheck --leak-check=full --track-origins=yes" \ -f testthat.R \ 2>&1 \ | tee out.log \ | cat
These tests can also be triggered on any pull request by leaving a review on the “Files changed” tab in a pull request:
/gha run r-valgrind
Projects listed here are not maintained or endorsed by the
LightGBM development team, but may offer some features currently missing from the main R package.
reticulate, a package used to call Python code from R. If you are comfortable with the added installation complexity of installing
lightgbm’s Python package and the performance cost of passing data between R and Python, you might find that this package offers some features that are not yet available in the native
For information about known issues with the R package, see the R-package section of LightGBM’s main FAQ page.