#CMAKE COMMAND INSTALL#

On both Windows, and macOS, a copy of R Framework is being embedded into JASP’s binary so that JASP can communicate with R without needing to rely on system’s R, or asking the user to install an instance of R. Upon the retrieval of results, JASP processes the results and generates a HTML page, and finally it displays it inside a Chromium WebEngine, i.e., QtWebEngine. Every command or analysis, one way or another, is being passed to an instance of R (via JASPEngine), and after a successful computation, the results are being communicated back to JASP’s GUI using a JSON object (via JASPEngine). JASP uses R as its computational back-end. My goal is to provide a high level overview of its architecture and components in order for you to be able to observe its complexity and hopefully find similar situations or solutions to/for your project. I am not intending to describe the entire architecture of JASP. It encapsulates an interface to R, as well as some logic on how the two apps needs to communicate to each other. The libR-Interface is a library developed by JASP Team. JASPEngine runs as a separate process alongside JASP, and uses libR-Interface ≅ R + RInside + Rcpp to run the R analyses and commands, and ultimately retrieve their results. The R part is responsible for calculation, and it is being executed in an R instance using the JASPEngine, and the QML part is being parsed by JASP to construct an ocean of check boxes 1 and controls for the user to interact with! JASP modules are specialized R packages consist of R, and some QML codes. In contrast, all the statistical analyses are done in R, and the results are being communicated back to the GUI using JSON objects. This means that the main body of the app is written in C++, i.e., GUI, Data Management, Engine. It is built on top of the Qt Framework, and R. JASP is an open-source alternative to SPSS, SAS, and other lookalikes.

#CMAKE COMMAND SOFTWARE#

I should mention that I will not be covering every aspects of the software or the build process equally. While this writing is very much focused on JASP project, and it might not directly apply to your project, I hope you can find bits and pieces of if helpful when you decide to go through the same process in your project. In addition, I will discuss how we have used CMake to work with R framework, and how we have used Conan to manage our dependencies in order to achieve a robust cross-platform, multi-architecture build, and deployment. It is a long journey of moving the entire build and deployment process from qmake to CMake. In this article, I will walk you through the process of rewriting JASP’s build system from scratch using CMake.

Cmake command