catala/build_system/dune

(library
 (name ninja_utils)
 (public_name ninja_utils)
 (modules ninja_utils)
 (libraries re))

(library
 (name clerk_driver)
 (public_name clerk.driver)
 (libraries
  catala.runtime_ocaml
  catala.catala_utils
  ninja_utils
  cmdliner
  re
  ocolor)
 (modules clerk_runtest clerk_driver))

(rule
 (target custom_linking.sexp)
 (mode fallback)
 (action
  (with-stdout-to
   %{target}
   (echo "()"))))

(executable
 (name clerk)
 (public_name clerk)
 (flags
  (:standard
   (:include custom_linking.sexp)))
 (libraries clerk.driver)
 (modules clerk)
 (package clerk))
feat(clerk): add basic ninja rule construction for test_scope 2022-02-05 21:22:46 +03:00			`(library`
			`(name ninja_utils)`
docs(clerk): add documentation about clerk and the Ninja_utils module 2022-02-24 15:45:16 +03:00			`(public_name ninja_utils)`
fix(clerk): unpath the build outputs to avoid writing corresponding files 2022-02-08 14:20:14 +03:00			`(modules ninja_utils)`
			`(libraries re))`
build(clerk/opam): add a clerk opam package and a clerk.driver library to test 2022-02-25 20:00:10 +03:00
			`(library`
			`(name clerk_driver)`
			`(public_name clerk.driver)`
feat(runtimes/jsoo): add a new class type duration with conv functions 2022-07-20 12:51:08 +03:00			`(libraries`
			`catala.runtime_ocaml`
Rename utils to catala_utils 2022-11-21 12:46:17 +03:00			`catala.catala_utils`
feat(runtimes/jsoo): add a new class type duration with conv functions 2022-07-20 12:51:08 +03:00			`ninja_utils`
			`cmdliner`
			`re`
Correctly setup ocolor on all output channels (and some cleanup of the remaining deps to ANSITerminal) 2023-06-08 13:06:27 +03:00			`ocolor)`
Clerk: split code for running tests from the main (Ninja) engine 2023-07-18 17:00:53 +03:00			`(modules clerk_runtest clerk_driver))`
build(clerk/opam): add a clerk opam package and a clerk.driver library to test 2022-02-25 20:00:10 +03:00
Add a script generating static builds We have an obvious limitation: static builds won't support plugins. We could resort to the classic method and do normal builds but on an old distrib to dodge compatibility issues. That would still be compatible with statically linking the more specific libs, like e.g. z3. 2022-08-03 16:03:33 +03:00			`(rule`
			`(target custom_linking.sexp)`
			`(mode fallback)`
			`(action`
			`(with-stdout-to`
			`%{target}`
			`(echo "()"))))`

build(clerk/opam): add a clerk opam package and a clerk.driver library to test 2022-02-25 20:00:10 +03:00			`(executable`
			`(name clerk)`
			`(public_name clerk)`
Add a script generating static builds We have an obvious limitation: static builds won't support plugins. We could resort to the classic method and do normal builds but on an old distrib to dodge compatibility issues. That would still be compatible with statically linking the more specific libs, like e.g. z3. 2022-08-03 16:03:33 +03:00			`(flags`
			`(:standard`
			`(:include custom_linking.sexp)))`
build(clerk/opam): add a clerk opam package and a clerk.driver library to test 2022-02-25 20:00:10 +03:00			`(libraries clerk.driver)`
			`(modules clerk)`
			`(package clerk))`