mirror of
https://github.com/CatalaLang/catala.git
synced 2024-09-19 16:28:12 +03:00
538e97dfd3
Runtimes for the various backends are expected to be made available from their own ecosystem. However, for convenience and to help with development settings (where the runtime might change), as part of installing catala they are put, in source form, into `<prefix>/lib/catala/runtime_LANG`. When using a dev version of Catala, and using Python, one would then just have to do `pip install <prefix>/lib/catala/runtime_python` within their venv to be able to run their python programs. |
||
|---|---|---|
| .. | ||
| clerk_driver.ml | ||
| clerk_driver.mli | ||
| clerk_runtest.ml | ||
| clerk_runtest.mli | ||
| clerk_scan.ml | ||
| clerk_scan.mli | ||
| clerk.ml | ||
| dune | ||
| README.md | ||
Clerk
The build system for Catala built on top of ninja.
Usage
Use clerk --help if you have installed it to get more information about the command line
options available. To get the development version of the help, run make help_clerk
after make build. The clerk binary corresponds to the Catala build system,
responsible for testing among other things.
Under the hood
To perform tests, Clerk will first generate a build.ninja file with required
rules and build statements retrieved from the given input path(s), before
executing the command ninja test.
The handling of the ninja structure is done with the module Ninja_utils.