From mboxrd@z Thu Jan  1 00:00:00 1970
From: elfring@users.sourceforge.net (SF Markus Elfring)
Date: Tue, 05 Mar 2013 11:42:39 +0100
Subject: [Cocci] Addition of source code documentation generation to the
 build system?
In-Reply-To: <alpine.DEB.2.02.1303051126520.1954@hadrien>
References: <5133B0BF.8000608@users.sourceforge.net>
 <alpine.DEB.2.02.1303041106480.1984@hadrien>
 <5134918E.7090304@users.sourceforge.net>
 <alpine.DEB.2.02.1303041338350.1984@hadrien>
 <5135B8DB.30307@users.sourceforge.net>
 <alpine.DEB.2.02.1303051028450.1954@hadrien>
 <5135C125.6070707@users.sourceforge.net>
 <alpine.DEB.2.02.1303051104310.1954@hadrien>
 <5135C74D.8000602@users.sourceforge.net>
 <alpine.DEB.2.02.1303051126520.1954@hadrien>
Message-ID: <5135CC1F.6090608@users.sourceforge.net>
To: cocci@systeme.lip6.fr
List-Id: cocci@systeme.lip6.fr

>> 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).


> 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.

Regards,
Markus