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.
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.