From: Josh Berdine <jjb@microsoft.com>
To: "caml-list@yquem.inria.fr" <caml-list@yquem.inria.fr>
Subject: ocamlbuild: ml -> cmx & cmi & o ?
Date: Wed, 15 Oct 2008 12:00:25 +0100 [thread overview]
Message-ID: <857DD0FDAC042B4485F9F5F4EA6751041E4CEEEDBC@EA-EXMSG-C332.europe.corp.microsoft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Hi,
I observe that ocamlbuild does not build cmx cmi and o files from a ml file (which has no associated mli) directly. Do others see different behavior? Instead it builds cmo and cmi from the ml using ocamlc, and then builds the cmx and o files from there using ocamlopt. Is there a reason I'm missing that ocamlbuild does not have a default rule for this case, using only one call to ocamlopt? If so, is there an easy way to do this with a plugin?
Cheers, Josh
[-- Attachment #2: Type: text/html, Size: 4137 bytes --]
next reply other threads:[~2008-10-15 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 11:00 Josh Berdine [this message]
2008-10-16 8:30 ` [Caml-list] " Romain Bardou
2008-10-16 8:43 ` Nicolas Pouillard
2008-10-16 8:53 ` Romain Bardou
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=857DD0FDAC042B4485F9F5F4EA6751041E4CEEEDBC@EA-EXMSG-C332.europe.corp.microsoft.com \
--to=jjb@microsoft.com \
--cc=caml-list@yquem.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