From: Francois BERENGER <berenger@bioreg.kyushu-u.ac.jp>
To: caml-list@inria.fr
Cc: sylvain@le-gall.net
Subject: Re: [Caml-list] with oasis, how to create setup.ml.exe ?
Date: Thu, 6 Jul 2017 08:52:51 +0900 [thread overview]
Message-ID: <53fb9d24-28fe-7e95-21ec-64579b6615b4@bioreg.kyushu-u.ac.jp> (raw)
In-Reply-To: <9f0cfe52-51db-6e38-67b8-1f4dd8949a91@planete-kraus.eu>
On 07/05/2017 06:28 PM, Vivien Kraus wrote:
> Hello,
> It is produced by the configure script from DevFiles, and not the
> setup.ml script.
OK, you are right and it fixed my problem.
However, oasis doesn't complain when
---
AlphaFeatures: compiled_setup_ml
---
is present but
---
Plugins: DevFiles (0.4)
---
is not.
I think it's a bug.
At least a warning should be generated in this case.
Or, maybe oasis should infer automatically the Plugins part.
Thanks for the help,
F.
> See your "configure script", it has a line for this :
>
> if [ ! -e setup.exe ] || [ _oasis -nt setup.exe ] || [ setup.ml -nt
> setup.exe ] || [ configure -nt setup.exe ]; then
> ocamlfind ocamlopt -o setup.exe setup.ml || ocamlfind ocamlc -o
> setup.exe setup.ml || exit 1
> rm -f setup.cmi setup.cmo setup.cmx setup.o setup.cmt
> fi
>
> Regards,
>
> Vivien
>
> Le 05/07/2017 à 10:20, Francois BERENGER a écrit :
>> Hello,
>>
>> I added AlphaFeatures: compiled_setup_ml
>> in my _oasis file, but I don't see this exe being produced.
>>
>> Are there some magic words I should pronounce (on the command line)
>> to make it appear?
>>
>> Which oasis step or invocation of 'ocaml setup.ml' is supposed to
>> produce it?
>>
>> Thanks,
>> F.
>>
>
next prev parent reply other threads:[~2017-07-05 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 8:20 Francois BERENGER
2017-07-05 9:28 ` Vivien Kraus
2017-07-05 23:52 ` Francois BERENGER [this message]
2017-07-06 7:29 ` Sylvain Le Gall
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=53fb9d24-28fe-7e95-21ec-64579b6615b4@bioreg.kyushu-u.ac.jp \
--to=berenger@bioreg.kyushu-u.ac.jp \
--cc=caml-list@inria.fr \
--cc=sylvain@le-gall.net \
/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).