Compiling flucoma-SC — python module error

Bug Reports and Issues
1

hi there,

I’m trying to compile flucoma-sc on my M1 machine and run into issues:

cmake -DSC_PATH=$HOME/vol/dev/sound/src/SuperCollider ..

runs fine, however

make install

results in

   [ 18%] Making SC docsTraceback (most recent call last):File “”, line 198, in _run_module_as_mainFile “”, line 88, in _run_codeFile “/Users/tboverma/vol/dev/sound/src/flucoma-sc/build/_deps/flucoma-docs-src/flucoma/MakeRef.py”, line 16, in from flucoma.doc import renderFile “/Users/tboverma/vol/dev/sound/src/flucoma-sc/build/_deps/flucoma-docs-src/flucoma/doc/render.py”, line 14, in from jinja2 import Environment, FileSystemLoader, select_autoescapeModuleNotFoundError: No module named ‘jinja2’make[2]: *** [CMakeFiles/MAKE_SC_REF] Error 1make[1]: *** [CMakeFiles/MAKE_SC_REF.dir/all] Error 2make: *** [all] Error 2

it seems that some python modules (jinja2) are missing? I’d rather not have to install it globally into my python environment…

Any help much appreciated

Till

2

Perhaps making a Python virtual environment or conda environment for this build is a good solution.

1 Like
3

uv has been my go to lately. It has simplified a lot of the annoying parts of tooling python.

If you make an environment with whatever tool you like then passing the path its executable to -DPython_EXECUTABLE should work when you configure cmake.

1 Like
4

I have some (uncommitted?) CMake changes to do this and, IIRC, run pip install to grab the dependencies. It’s slightly horrible.

In practice, the easiest thing at the moment for people just trying to do a minimum-hassle build is to specify -DDOCS=OFF to avoid all the python horribleness, and then grab the docs from a downloaded package.

What we’re going to try transitioning to is to generate the docs on CI and just have cmake pull those already baked files as a dependency by default. Again, I have a half-finished, uncommitted implementation waiting for some attention.

1 Like