From a04f77dca1c4116d27c41a6dfabb40e3c2cf09de Mon Sep 17 00:00:00 2001 From: Rudi Grinberg Date: Sun, 19 Aug 2018 19:03:19 +0300 Subject: [PATCH] Update configurator to use dune syntax Signed-off-by: Rudi Grinberg --- doc/configurator.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/configurator.rst b/doc/configurator.rst index 44a7bb5e..e16de2c3 100644 --- a/doc/configurator.rst +++ b/doc/configurator.rst @@ -63,12 +63,12 @@ invoke it as an executable and tell dune about the targets that it produces: .. code-block:: lisp (executable - ((name discover) - (libraries (dune.configurator)))) + (name discover) + (libraries dune.configurator)) (rule - ((targets (config.h)) - (action (run ./discover.exe)))) + (targets config.h) + (action (run ./discover.exe))) Another common pattern is to produce a flags file with configurator and then use this flag file using ``:include``: @@ -76,9 +76,9 @@ this flag file using ``:include``: .. code-block:: lisp (library - ((name mylib) - (c_names (foo)) - (c_library_flags (:include (flags.sexp))))) + (name mylib) + (c_names foo) + (c_library_flags (:include (flags.sexp)))) For this, generate the list of flags for your library — for example using ``Configurator.V1.Pkg_config`` — and then write them to a file,