Code Run Build

When you need to configure, build, test, or deploy ORE Studio via CMake — or generate PlantUML diagrams as part of a build.

1. Identify the operation. Pick from the Recipes list below.
2. Open the matching recipe and follow its numbered steps. Each recipe is a single how_do_i_*.org file with executable babel blocks.
3. Run from the repo root. The babel blocks are configured to use the repo root as their cwd; if you run commands outside emacs, cd there first.
4. Default preset: read ORES_PRESET from .env (compass build does this automatically) unless the user specifies otherwise. The recipe shows how to list the alternatives.
5. Always go through compass build, never raw cmake — including configure. compass build resolves the preset from .env and configures the build directory automatically on first use, so a separate cmake --preset configure step is never needed. Multiple worktrees on this host build concurrently; compass build takes a host-wide lock first (two slots, capped -j2=/-j3=) so builds don't corrupt each other's shared library outputs — raw cmake --preset=/=cmake --build invocations bypass that lock entirely and are never the right call, even "just to configure" or "just to build one target". If it prints a waiting message, let it wait — that's expected, not a hang. ./compass.sh build --status shows who holds each slot. See How do I build the system? for detail.

• How do I list available presets?
• How do I configure the project?
• How do I build the system?
• How do I run the tests?
• How do I enable test logging?
• How do I deploy the site?
• How do I deploy the skills?
• How do I generate PlantUML diagrams?

• CMake setup — preset menu, output directory layout, build types, parallel builds, compass build, and the test-logging knobs.