caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Hendrik Tews <tews@cs.ru.nl>
To: Sam Steingold <sds@gnu.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] otags and OMakefile
Date: 11 Aug 2006 15:53:11 +0200	[thread overview]
Message-ID: <wwu1wrncraw.fsf@tandem.cs.kun.nl> (raw)
In-Reply-To: <ebfm03$gjh$1@sea.gmane.org>

Sam Steingold <sds@gnu.org> writes:

   what is the correct entry for TAGS in OMakefile?
   
   I have this in the top-level OMakefile:
   ------------------------------------------------------------------
   TAGS:
   	otags -r $(SRC_DIRS)
   ------------------------------------------------------------------

This only works in simple cases (and, apparently, your case is
not simple).

   1. somehow otags tries to read non-ml files (despite "otags -h"

It does a Unix.stat on the files before filtering, which only
works for files smaller 1GB. 

Granted, this is a bug.

   2. otags does not respect the pre-processors used for some files,
   resulting in many errors:

You have to specify the preprocessors on the otags command line, like

   otags -pa pr_r.cmo revised.ml

You might have to add -libdir dir_of_camlp4_module.

   the preprocessing is specified in OMakeroot:

I have no idea about OMakefile, but I doubt it can work as you
expected. What you have to (or OMakefile would have) is the
following:
- collect the source files in equivalence sets according to the needed
  preprocessors 
- invoke otags on each such set separately with the right set of
  -pa options
- concat the results 

(With -v you can see the camlp4 calls that do the real job. )

Bye,

Hendrik Tews


  parent reply	other threads:[~2006-08-11 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 16:13 Sam Steingold
2006-08-11  5:56 ` [Caml-list] " Nathaniel Gray
2006-08-11 13:53 ` Hendrik Tews [this message]
2006-08-16 15:51   ` Sam Steingold

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=wwu1wrncraw.fsf@tandem.cs.kun.nl \
    --to=tews@cs.ru.nl \
    --cc=caml-list@inria.fr \
    --cc=sds@gnu.org \
    /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).