Skip to content

Commit 94f635e

Browse files
avsmemillon
authored andcommitted
doc: use DUNE_GEN instead of JBUILDER_GEN (#1725)
Both symbols are supported, but of course `DUNE_GEN` is the preferred one in new code. Signed-off-by: Anil Madhavapeddy <[email protected]>
1 parent da3f9d0 commit 94f635e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/advanced-topics.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,15 +19,15 @@ In order to do that, write or setup a rule to generate a
1919
``META.<package>.template`` file in the same directory as the
2020
``<package>.opam`` file. Dune will generate a ``META.<package>``
2121
file from the ``META.<package>.template`` file by replacing lines of
22-
the form ``# JBUILDER_GEN`` by the contents of the ``META`` it would
22+
the form ``# DUNE_GEN`` by the contents of the ``META`` it would
2323
normally generate.
2424

2525
For instance if you want to extend the ``META`` file generated by
2626
dune you can write the following ``META.foo.template`` file:
2727

2828
.. code::
2929
30-
# JBUILDER_GEN
30+
# DUNE_GEN
3131
blah = "..."
3232
3333
Findlib integration and limitations

0 commit comments

Comments
 (0)