From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id B595F7F30A for ; Tue, 5 Mar 2013 16:45:16 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of elfring@users.sourceforge.net) identity=pra; client-ip=212.227.15.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="elfring@users.sourceforge.net"; x-sender="elfring@users.sourceforge.net"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of elfring@users.sourceforge.net) identity=mailfrom; client-ip=212.227.15.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="elfring@users.sourceforge.net"; x-sender="elfring@users.sourceforge.net"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mout.web.de) identity=helo; client-ip=212.227.15.3; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="elfring@users.sourceforge.net"; x-sender="postmaster@mout.web.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkcEADARNlHU4w8DkGdsb2JhbABEwkoEBIEDFg4BAQEBCQkUFCeDHj0WGAMCAQIBWAgBAReHfJwWkRWQNY8pgyoDlkqFZBOOAA X-IPAS-Result: AkcEADARNlHU4w8DkGdsb2JhbABEwkoEBIEDFg4BAQEBCQkUFCeDHj0WGAMCAQIBWAgBAReHfJwWkRWQNY8pgyoDlkqFZBOOAA X-IronPort-AV: E=Sophos;i="4.84,787,1355094000"; d="scan'208";a="5609582" Received: from mout.web.de ([212.227.15.3]) by mail2-smtp-roc.national.inria.fr with ESMTP; 05 Mar 2013 16:45:16 +0100 Received: from [192.168.1.215] ([78.49.195.40]) by smtp.web.de (mrweb003) with ESMTPA (Nemesis) id 0LeLWP-1UaRZm27FF-00qWd8 for ; Tue, 05 Mar 2013 16:45:15 +0100 Message-ID: <5136130A.3060306@users.sourceforge.net> Date: Tue, 05 Mar 2013 16:45:14 +0100 From: SF Markus Elfring User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:vMOQqV3rwvRaST9nAdUZ81ZaDfZzPQRI8nPCtGPqMnJ mowPgwXvdIWdOGABbhGunqCTWhQXFImXCH1nD1B2rjf93bBlbG zewbQ5F9ckDLrETl48WbkMbj8MxM4np7taFUEQ+GJUKZVbU1BM j2e3gKBCIvjr6trLxiu2QPp9FKyKSCpX/OepuKcMecHA3K2lqN P/efBblmgJlO3fV6ArK5w== Subject: [Caml-list] Automatic generation of source code documentation 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