caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: caml-list@inria.fr
Cc: David Allsopp <dra-news@metastack.com>
Subject: Re: [Caml-list] Addition of a data export variant containing only required extensions for build dependency specifications
Date: Tue, 25 Jul 2017 20:13:26 +0200	[thread overview]
Message-ID: <29d73776-055e-50a0-da32-646d884ad39b@users.sourceforge.net> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9014D5206DE@Remus.metastack.local>

> Your descriptions are, I'm afraid, vague, don't give a simple repro case,
> or the output you're expecting.

The tool “ocamldep” writes dependency specifications (by a default setting)
which should be handled by a software build system for the programming language
“OCaml” already.
I suggest to add a data export variant which will omit such duplicate information.
I hope that a bit less data could be written so that there will be also no need
for extra processing with questionable specifications by the build system.


elfring@Sonne:~/Projekte/Bau> sources='my_test1.ml my_test1.mli' && touch ${sources} && ocamldep ${sources}
my_test1.cmo : my_test1.cmi
my_test1.cmx : my_test1.cmi
my_test1.cmi :


Regards,
Markus

      parent reply	other threads:[~2017-07-25 18:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 19:21 [Caml-list] Development status of the dependency generator for OCaml SF Markus Elfring
2017-07-21  9:19 ` David Allsopp
2017-07-21 11:30   ` SF Markus Elfring
2017-07-21 13:01     ` David Allsopp
2017-07-21 15:50       ` SF Markus Elfring
2017-07-21 16:16         ` David Allsopp
2017-07-21 17:07           ` SF Markus Elfring
2017-07-25 18:13           ` SF Markus Elfring [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=29d73776-055e-50a0-da32-646d884ad39b@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=dra-news@metastack.com \
    /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).