R Development Page
Contributed R Packages
Below is a list of all packages provided by project RInside - R inside C++.
Important note for package binaries: R-Forge provides these binaries only for the most recent version of R, but not for older versions. In order to successfully install the packages provided on R-Forge, you have to switch to the most recent version of R or, alternatively, install from the package sources (.tar.gz).
C++ classes to embed R in C++ applications
|C++ classes to embed R in C++ applications The RInside packages makes it easier to have R inside your C++ application by providing a C++ wrapper class providing the R interpreter. As R itself is embedded into your application, a shared library build of R is required. This works on Linux, OS X and even on Windows provided you use the same tools used to build R itself. Numerous examples are provided in the six subdirectories of the examples/ directory of the installed package: standard, mpi (for parallel computing) qt (showing how to embed RInside inside a Qt GUI application), wt (showing how to build a web-application using the Wt toolkit), armadillo (for RInside use with RcppArmadillo) and eigen (for RInside use with RcppEigen). Doxygen-generated documentation of the C++ classes is available at the RInside website as well.|
|Version: 0.2.10.1 | Last change: 2013-08-11 15:46:54+02 | Rev.: 275|
|Download: (.tar.gz) | (.zip) | Build status: Current | Stable Release: Get RInside 0.2.14 from CRAN|
R install command:
Build status codes
0 - Current: the package is available for download. The corresponding package passed checks on the Linux and Windows platform without ERRORs.
1 - Scheduled for build: the package has been recognized by the build system and provided in the staging area.
2 - Building: the package has been sent to the build machines. It will be built and checked using the latest patched version of R. Note that it is included in a batch of several packages. Thus, this process will take some time to finish.
3 - Failed to build: the package failed to build or did not pass the checks on the Linux and/or Windows platform. It is not made available since it does not meet the policies.
4 - Conflicts: two or more packages of the same name exist. None of them will be built. Maintainers are asked to negotiate further actions.
5 - Offline: the package is not available. The build system may be offline or the package maintainer did not trigger a rebuild (done e.g., via committing to the package repository).
If your package is not shown on this page or not building, then check the build system status report.