From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocamlbuild, build a source that starts with _
Date: Tue, 9 Feb 2016 09:47:43 -0500 [thread overview]
Message-ID: <CAPFanBGa6E+E4mv=kkftE-guTww+m+xnapfZY+BS0EqcJSBDow@mail.gmail.com> (raw)
In-Reply-To: <961B600BF0C94937844621CB3C800690@erratique.ch>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
Well, it is still possible to work around this issue by re-doing the
slurping from the plugin:
https://gitlab.com/gasche-snippets/ocamlbuild-underscored-files/blob/master/myocamlbuild.ml
I wouldn't mind removing that test from future ocamlbuild releases -- as of
now I don't see any problem with "_oasis" or other "_tags" file being
considered parts of the build tree.
On Tue, Feb 9, 2016 at 9:45 AM, Daniel Bünzli <daniel.buenzli@erratique.ch>
wrote:
> Le mardi, 9 février 2016 à 14:35, Daniel Bünzli a écrit :
> > Hello,
> >
> > It seems I can't convince ocamlbuild to build (i.e. copy) a source that
> starts with `_`.
> > Is there a workaround ?
>
> I guess this must be due to this line (though I have to admit that I have
> hard time to understand ocamlbuild's convoluted control flow).
>
> https://github.com/ocaml/ocamlbuild/blob/master/src/main.ml#L150
>
> so the answer seems to be no, which is quite annoying.
>
> Daniel
>
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
[-- Attachment #2: Type: text/html, Size: 2175 bytes --]
next prev parent reply other threads:[~2016-02-09 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 13:35 Daniel Bünzli
2016-02-09 14:45 ` Daniel Bünzli
2016-02-09 14:47 ` Gabriel Scherer [this message]
2016-02-09 15:06 ` Daniel Bünzli
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='CAPFanBGa6E+E4mv=kkftE-guTww+m+xnapfZY+BS0EqcJSBDow@mail.gmail.com' \
--to=gabriel.scherer@gmail.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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).