From: David Allsopp <dra-news@metastack.com>
To: Markus Mottl <markus.mottl@gmail.com>
Cc: OCaml List <caml-list@inria.fr>
Subject: RE: [Caml-list] Building pcre-ocaml 7.0.2 on MinGW
Date: Wed, 19 Jun 2013 15:08:26 +0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D9CC8534ED@Remus.metastack.local> (raw)
In-Reply-To: <CAP_800qKopp8EiauB9UgsxC3-7xOzgfEGcnuOkmZgDcDU7eU8g@mail.gmail.com>
Markus Mottl wrote:
> I have no experience with OCaml installations on Windows, but what
> concerns the configuration of pcre-ocaml, it actually does use pcre-
> config. If the latter is not in your path, you can add the configure flag
> "--with-pcre-config {full path to pcre-config}" to make it work.
The problem is more subtle than that - pcre-config is there but it's a shell script which means that make (which uses sh) can execute it but ocamlbuild (which uses cmd on a Windows build) cannot. Arguably it's a deficiency of the Windows build of PCRE that it doesn't generate a .cmd version of pcre-config (but that's another m4 related headache!). I made the following two changes for my build environment:
After running ./configure (but therefore before make install) for PCRE:
sed -i -e "1s/$/\n\nPATH=\/bin:\$PATH/" pcre-config
(that's necessary because when bash is invoked from a command shell it will interpret the Windows PATH and you need access to uname and test from Cygwin's /bin)
And then after installing I created pcre-config.cmd in the same directory as pcre-config (and therefore in my PATH as that's my OCaml bin directory):
@setlocal
@echo off
bash /cygdrive/c/Dev/OCaml/bin/pcre-config %*
It's possible that ocamlbuild could workaround this without the need for the extra script, but it's probably better to fix PCRE itself...
David
next prev parent reply other threads:[~2013-06-19 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 14:36 David Allsopp
2013-06-19 14:43 ` Markus Mottl
2013-06-19 15:08 ` David Allsopp [this message]
2013-06-19 16:32 ` Adrien Nader
2013-06-19 16:45 ` Markus Mottl
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=E51C5B015DBD1348A1D85763337FB6D9CC8534ED@Remus.metastack.local \
--to=dra-news@metastack.com \
--cc=caml-list@inria.fr \
--cc=markus.mottl@gmail.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