public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Addition of source code documentation generation to the build system?
Date: Sun, 03 Mar 2013 21:21:19 +0100	[thread overview]
Message-ID: <5133B0BF.8000608@users.sourceforge.net> (raw)

Hello,

I try to generate some documentation from the source files of your current software.

elfring at Sonne:~/Projekte/Coccinelle/lokal> MY_DIR=../Probe/Doku/ &&
MY_NAMES=${MY_DIR}file_name_list11.txt && find . \( -name '*.ml' -o -name
'*.mli' \) -a ! -name 'myocamlbuild.ml' -type f -fprint0 $MY_NAMES &&
ocamldoc.opt -d ${MY_DIR} -I commons -I commons/ocamlextra -I
commons/ocollection -I globals -I engine -I parsing_c -I parsing_cocci -I ctl -I
ocaml -I ocamlsexp -I python -I popl09 -I extra -I /usr/local/share/menhir -I
bundles/pcre -I bundles/pycaml -dot -o ${MY_DIR}my_graph.gv -html $(sed 's/\x0/
/g' $MY_NAMES)


I get a couple of error messages because my approach is incomplete so far. I
stumble on technical challenges here.
Would you like to suggest an improved way for the construction of include
directories and file names which should be passed to the command?
Are there any chances to adapt it to the chosen build configuration?

Regards,
Markus

             reply	other threads:[~2013-03-03 20:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 20:21 SF Markus Elfring [this message]
2013-03-04 10:10 ` [Cocci] Addition of source code documentation generation to the build system? 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
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=5133B0BF.8000608@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --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