From e5b8d638ea7293ae8a6d65386aefbb0d30aa254c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 28 Aug 2017 16:36:33 +0200 Subject: Update user guide --- guide/edoc.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'guide/edoc.html') diff --git a/guide/edoc.html b/guide/edoc.html index 5203a39..49f40c0 100644 --- a/guide/edoc.html +++ b/guide/edoc.html @@ -33,13 +33,13 @@ div.navfooter{margin-bottom:1em}
-
Prev   Next

Chapter 14. EDoc comments

Erlang.mk provides a thin wrapper on top of EDoc, an application -that generates documentation based on comments found in modules.

14.1. Writing EDoc comments

The EDoc user guide -explains everything you need to know about EDoc comments.

14.2. Configuration

The EDOC_OPTS variable allows you to specify additional +

Prev   Next

Chapter 15. EDoc comments

Erlang.mk provides a thin wrapper on top of EDoc, an application +that generates documentation based on comments found in modules.

15.1. Writing EDoc comments

The EDoc user guide +explains everything you need to know about EDoc comments.

15.2. Configuration

The EDOC_OPTS variable allows you to specify additional EDoc options. Options are documented in the EDoc manual.

A common use for this variable is to enable Markdown in doc comments, using the edown application:

DOC_DEPS = edown
-EDOC_OPTS = {doclet, edown_doclet}

14.3. Usage

To build all documentation, you would typically use:

$ make docs

Do note, however, that EDoc comments will only be generated +EDOC_OPTS = {doclet, edown_doclet}

15.3. Usage

To build all documentation, you would typically use:

$ make docs

Do note, however, that EDoc comments will only be generated automatically if the doc/overview.edoc file exists. If you do not want that file and still want to generate doc comments, two solutions are available.

You can generate EDoc documentation directly:

$ make edoc

You can enable automatic generation on make docs by adding -- cgit v1.2.3