public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
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:49:09 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.02.1303051145190.1954@hadrien> (raw)
In-Reply-To: <5135CC1F.6090608@users.sourceforge.net>

On Tue, 5 Mar 2013, SF Markus Elfring wrote:

> >> I guess that I will need a technique to determine include paths for the
> >> referenced modules consistently.
> >
> > I think you could grep for them in the makefile.
>
> This approach will not work because the "Makefile" will be generated by the
> configuration script (build specification).

It would seem reasonable to run configure first.

But anyway, I don't think that the configureation script generates the
makefiles.  The make files are static, and they include other files that
are generated by the configuration file.  But the include information is
in the static part.

> > I don't know anything about this tool, but I would expect that it would
> > follow the same strategy as the rest of the ocaml tools for respolving
> > dependencies.
>
> I would also appreciate if the program "ocamldoc" could eventually benefit more
> from the OCaml infrastructure to make the approach a bit more convenient and
> safe.   ;-)
> I find that the challenge remains to construct relevant parameters by usual
> software development (with M4 programming language) here.

I think you should take it up with the ocaml developers.  Surely others
would appreciate this functionality, if it does not already exist.

julia

  reply	other threads:[~2013-03-05 10:49 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
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 [this message]
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.1303051145190.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