caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Maxence Guesdon <Maxence.Guesdon@inria.fr>
To: caml-list@inria.fr
Cc: Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com>
Subject: Re: [Caml-list] ocamldoc ... "Warning: Module or module type BatSet.StringSet not found"
Date: Tue, 8 Oct 2013 19:44:40 +0200	[thread overview]
Message-ID: <20131008194440.425e2d19@alcazar> (raw)
In-Reply-To: <52541870.7040000@gmail.com>

On Tue, 08 Oct 2013 15:36:32 +0100
Matej Kosik <5764c029b688c1c0d24a2e97cd764f@gmail.com> wrote:

> Hi,
> 
> A couple of weeks ago I started to use ocamldoc.
> In certain situation, it gives me:
> 
> 	"Warning: Module or module type BatSet.StringSet not found"
> 
> The simplest "program" that triggers it is:
> 
> 	module StringSet = BatSet.StringSet
> 
> I get it with the following command:
> 
> 	ocamlfind doc -html -package batteries main.ml
> 
> I thought that some -I path was missing, so I tried:
> 
> 	ocamlfind doc -html -thread -package batteries `ocamlfind query -i-format -recursive batteries` main.ml
> 
> but the warning remains.
> 
> It is not a big deal but I still wonder why I get it.
> ((The program itself compiles without kind of warning.))

This message is not about not finding libraries so adding -I options is useless.

ocamldoc complains about not finding ocamldoc information about
BatSet.StringSet to create cross reference links in documentation.

To fix it, you have to give sources of BatSet on the ocamldoc command
line, or use the -load option to load an ocamldoc dump produced from
the BatSet sources.

Regards,

Maxence

      parent reply	other threads:[~2013-10-08 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 14:36 Matej Kosik
2013-10-08 15:24 ` Ashish Agarwal
2013-10-08 16:59   ` Matej Kosik
2013-10-08 17:29     ` Ashish Agarwal
2013-10-08 17:44 ` Maxence Guesdon [this message]

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=20131008194440.425e2d19@alcazar \
    --to=maxence.guesdon@inria.fr \
    --cc=5764c029b688c1c0d24a2e97cd764f@gmail.com \
    --cc=caml-list@inria.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;
as well as URLs for NNTP newsgroup(s).