From: David Allsopp <dra-news@metastack.com>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>,
whitequark <whitequark@whitequark.org>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: RE: [Caml-list] [ANN] opam-cross-windows
Date: Tue, 15 Mar 2016 09:12:37 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9EA36FC8F@Remus.metastack.local> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CEA76CE@IRSMSX102.ger.corp.intel.com>
Soegtrop, Michael wrote:
> One more question: on Windows there is (or was) a circular dependency
> between flexdll and Ocaml. One of the two needs to be installed in binary
> form. Did you also run into this issue? If so, how did you solve it?
I haven't yet updated the build documentation (because it needs a wholesale rewrite), but in trunk (and 4.03), the circular dependency is gone.
1. Ensure FlexDLL sources are in flexdll/ in the OCaml build tree
1a. If you're building from a git clone, issue git submodule update --init
1b. If you're building from a sources tarball, issue git clone https://github.com/alainfrisch/flexdll.git
2. Follow usual configuration steps in config/
3. make -f Makefile.nt flexdll world opt opt.opt install
flexlink.exe (and the .manifest files for the MSVC ports) are installed to bin. flexlink.exe will be a bytecode executable unless opt.opt is compiled. The correct .o/.obj files are installed to lib. Note that FlexDLL 0.35 or later is required, so you can't yet use a FlexDLL sources tarball.
Note that this procedure is not (yet) available for building the FlexDLL for Cygwin (because that uses the configure, rather than Makefile.nt route, and at this stage I didn't have the time to put the changes in both places...)
David
next prev parent reply other threads:[~2016-03-15 9:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 9:02 whitequark
2016-03-14 19:55 ` Martin DeMello
2016-03-14 20:14 ` Adrien Nader
2016-03-14 20:26 ` Martin DeMello
2016-03-14 20:39 ` Adrien Nader
2016-03-14 21:10 ` Martin DeMello
2016-03-15 8:37 ` whitequark
2016-03-15 8:26 ` Soegtrop, Michael
2016-03-15 8:36 ` whitequark
2016-03-15 8:53 ` Soegtrop, Michael
2016-03-15 8:56 ` whitequark
2016-03-15 11:29 ` Soegtrop, Michael
2016-03-16 14:27 ` Andreas Hauptmann
2016-03-15 9:18 ` Adrien Nader
2016-03-15 9:12 ` David Allsopp [this message]
2016-05-20 18:38 ` Boutillier, Pierre
2016-05-20 18:45 ` whitequark
2016-05-23 8:24 ` Soegtrop, Michael
2016-05-24 6:57 ` whitequark
2016-05-24 12:35 ` Adrien Nader
2016-05-23 9:53 ` Mauricio Fernández
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=E51C5B015DBD1348A1D85763337FB6D9EA36FC8F@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=caml-list@inria.fr \
--cc=michael.soegtrop@intel.com \
--cc=whitequark@whitequark.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).