From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Addition of source code documentation generation to the build system?
Date: Tue, 5 Mar 2013 11:06:14 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1303051104310.1954@hadrien> (raw)
In-Reply-To: <5135C125.6070707@users.sourceforge.net>
> The file search gave unwanted results when I attempted it with the complete
> project hierarchy. I imagine that usable file name lists can be automatically
> generated if all your own source files (excluding bundled components) would be
> stored in specific subdirectories. Several parts can be concatenated to achieve
> the desired parameters for the call of the tool "ocamldoc".
To the best of my understanding, our files are in separate directories
from the files for external libraries. But if you need everything to get
any documentation, then I guess you would need the external libraries as
well.
I'm not sure why ocamldoc can't just use the -I paths to find the things
it needs. That is you should be able to give just one file, and it should
be able to find the information for any dependencies. But i haven't tried
it either.
julia
next prev parent reply other threads:[~2013-03-05 10:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 20:21 [Cocci] Addition of source code documentation generation to the build system? SF Markus Elfring
2013-03-04 10:10 ` Julia Lawall
2013-03-04 12:20 ` SF Markus Elfring
2013-03-04 12:42 ` Julia Lawall
2013-03-04 12:57 ` SF Markus Elfring
2013-03-04 13:09 ` Julia Lawall
2013-03-05 9:20 ` SF Markus Elfring
2013-03-05 9:30 ` Julia Lawall
2013-03-05 9:55 ` SF Markus Elfring
2013-03-05 10:06 ` Julia Lawall [this message]
2013-03-05 10:22 ` SF Markus Elfring
2013-03-05 10:28 ` Julia Lawall
2013-03-05 10:42 ` SF Markus Elfring
2013-03-05 10:49 ` Julia Lawall
2013-03-05 13:24 ` SF Markus Elfring
2013-03-05 16:34 ` Arie Middelkoop
2013-03-05 17:08 ` SF Markus Elfring
2013-03-05 20:44 ` SF Markus Elfring
2013-03-07 9:55 ` SF Markus Elfring
2013-03-05 16:01 ` SF Markus Elfring
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=alpine.DEB.2.02.1303051104310.1954@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.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