From: SF Markus Elfring <elfring@users.sourceforge.net>
To: caml-list@inria.fr
Subject: [Caml-list] Automatic generation of source code documentation
Date: Tue, 05 Mar 2013 16:45:14 +0100 [thread overview]
Message-ID: <5136130A.3060306@users.sourceforge.net> (raw)
Hello,
I would like to generate some documentation from the source files of a project
which uses an Autotools build specification. I try to use the tool "ocamldoc"
for this purpose.
I find that there are some difficulties for which I am looking for reusable
solutions. How do you determine relevant file name lists and corresponding
include paths for the involved software components automatically?
Which configuration options and command parameters should be considered to
adjust documentation variants?
I would appreciate your advices.
Regards,
Markus
reply other threads:[~2013-03-05 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5136130A.3060306@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).