Build and run
quarry builds the project it has open, merges the compiler's diagnostics into Problems, and runs the binary it produced.
Builds
| Project | What runs |
|---|---|
| Cargo | cargo build --message-format=json, diagnostics parsed from the JSON |
| CMake | configure, then build with the selected configuration |
| C/C++ with no build system | a plain clang compile of the sources |
Builds are available in Debug and Release. The profile is remembered for the session and passed through to the build command.
Run configurations
A run configuration is the whole form: program, arguments, working directory and environment. The form validates as you type — a relative working directory is refused, and the argv preview shows exactly what will be executed.
- Opening a project prefills the form:
cargo metadatanames the Cargo binary, and a CMake project gets its conventional output path, named even before the first build. - Configurations can be saved under a name, updated and deleted. Empty and duplicate names are refused.
- The run log offers Copy output (ANSI-stripped), Copy argv, and Re-run with the same program, arguments, working directory and environment.
The terminal
The embedded terminal is a real PTY, so interactive programs, progress bars and full-screen editors behave. Placement, font family and size are settings; the default places it beside the editor.
Tests are a build too
Test discovery and execution come from the same toolchain: Cargo tests are listed from the crate metadata, run individually or as a group. See Tests.
Next
Debugging starts the built binary under lldb.