How do I configure the project?
For the preset menu and what each axis means, see CMake setup.
Question
How do I configure ORE Studio with CMake?
Answer
Configure via compass build, never raw cmake --preset — it takes
the host-wide build lock (see Build locking in How do I build the
system?) before touching the shared build directory, which a bare
cmake --preset bypasses entirely:
./compass.sh build
compass build resolves the preset from ORES_PRESET in .env (or
--preset <name> to override) and configures the build directory
automatically on first use — there is no separate configure step to
run by hand. The preset's build directory is created at
build/output/<preset>/. To list available presets see
How do I list available presets?.
Re-configuring with options
compass build has no pass-through for raw -D<NAME>=<VALUE> CMake
options — its configure step is a fixed cmake --preset <preset>
with no flag injection. Test logging (the one case that recipe
authors reach for -D for) is controlled a different way, via
.env variables forwarded by CMakeLists.txt, not a CMake cache
option — see How do I enable test logging?.
Script
The commands above. No wrapper.
Tested by
CI workflows configure every preset on every push.
See also
- CMake setup — preset naming, build types.
- How do I list available presets?
- How do I build the system? — next step after configure.