Assemble the rest of the morie family from R

The R-side entry to the morie "bricklayer": from an R session it reports which family members are present and offers to install the ones that are missing. You are already in R with rmorie, so this focuses on the Python side (morie via pip) and on verifying the shared C/C++ numeric core. The proprietary rmorie-cli is never auto-installed – only pointed to.

Usage

morie_bricklayer(yes = FALSE, check = FALSE)

Arguments

yes

Logical; install without prompting (default FALSE).

check

Logical; report status only, install nothing (default FALSE).

Value

Invisibly, a named logical vector of what is present.

Details

The whole family is built on one shared C/C++ core (libmorie -> morie._core in Python; rmoriebricklayer's compiled kernels in R). Without a C/C++ toolchain the packages fall back to slow pure-language kernels or fail to build from source, so this also checks the toolchain and whether the compiled backend actually loaded.

Examples

# \donttest{
morie_bricklayer(check = TRUE)
#> morie family status:
#>   [ ] morie            (Python / pip)
#>   [x] rmorie           (R / this session)
#>   [x] rmoriedata       (R)
#>   [x] rmoriebricklayer (R / shared C core)
#>   [ ] rmorie-cli       (proprietary -- not auto-installed)
#>   [x] C/C++ toolchain  (cc + c++ -- REQUIRED for the compiled core)
#> 
morie_bricklayer()
#> morie family status:
#>   [ ] morie            (Python / pip)
#>   [x] rmorie           (R / this session)
#>   [x] rmoriedata       (R)
#>   [x] rmoriebricklayer (R / shared C core)
#>   [ ] rmorie-cli       (proprietary -- not auto-installed)
#>   [x] C/C++ toolchain  (cc + c++ -- REQUIRED for the compiled core)
#> 
#> note: rmorie-cli is proprietary (Receipt-of-Custody); obtain it at https://github.com/rootcoder007/rmorie-cli 
#> Non-interactive; not installing. Run with yes = TRUE, or:
#>   /usr/bin/python3 -m pip install morie
# }