From 0e0d87500f87a9c1a700540cee23429659742365 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=A1s=20Ojeda=20B=C3=A4r?= Date: Tue, 20 Aug 2019 08:24:49 +0200 Subject: [PATCH] Doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Nicolás Ojeda Bär --- doc/dune-files.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/dune-files.rst b/doc/dune-files.rst index edc039afa72..cbc817fe601 100644 --- a/doc/dune-files.rst +++ b/doc/dune-files.rst @@ -595,6 +595,16 @@ Executables can also be linked as object or shared object files. See ``executable`` stanza will cause Dune to copy the ``.exe`` files to the source tree and ``dune clean`` to delete them +- ``(c_names ())``, if your executable needs C stubs, you must list the C + files in this field, without the ``.c`` extension + +- ``(cxx_names ())`` is the same as ``c_names`` but for C++ stubs + +- ``(c_flags )`` specifies the compilation flags for C stubs, using the + :ref:`ordered-set-language`. This field supports ``(:include ...)`` forms + +- ``(cxx_flags )`` is the same as ``c_flags`` but for C++ stubs + Linking modes ~~~~~~~~~~~~~ @@ -676,6 +686,9 @@ version is the same as the ``.bc`` one except that it is linked with the ``-custom`` option of the compiler. You should always use the ``.exe`` rather that the ``.bc`` inside build rules. +Lastly, note that ``.bc`` executables cannot contain C stubs. If your executable +contains C stubs you may want to use ``(modes exe)``. + executables -----------