caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Markus Mottl <markus.mottl@gmail.com>
To: Adrien Nader <adrien@notk.org>
Cc: David Allsopp <dra-news@metastack.com>, OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Building pcre-ocaml 7.0.2 on MinGW
Date: Wed, 19 Jun 2013 12:45:50 -0400	[thread overview]
Message-ID: <CAP_800pVRwyNH+dej16+37qKfrgvw-BEshmQJp3kFdSMLGncfQ@mail.gmail.com> (raw)
In-Reply-To: <20130619163255.GA27108@notk.org>

It would certainly be easy to switch to pkg-config.  I just don't know
which tool is considered the most portable choice for pcre.  I haven't
heard from others yet that they had problems with pcre-config so I'm
not sure switching will improve things.  FWIW, both pcre-config and
pkg-config seem to be working fine on Mac OS X and on CentOS.

Regards,
Markus

On Wed, Jun 19, 2013 at 12:32 PM, Adrien Nader <adrien@notk.org> wrote:
> Hi,
>
> I haven't tried anything with pcre but generally-speaking, these
> foo-config need to die in favor of pkg-config.
> My linux installation has around 70 of them and they all duplicate the
> same functionality, usually badly.
>
> Hopefully, there is pkg-config support for pcre and the best thing to do
> is probably to change the bindings to use pkg-config instead of
> pcre-config. The arguments are the same so it should be fairly painless
> (you only have to call "pkg-config libpcre" instead of "pcre-config").
>
> Hope this helps,
> Adrien Nader



-- 
Markus Mottl        http://www.ocaml.info        markus.mottl@gmail.com

      reply	other threads:[~2013-06-19 16:46 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
2013-06-19 16:32     ` Adrien Nader
2013-06-19 16:45       ` Markus Mottl [this message]

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=CAP_800pVRwyNH+dej16+37qKfrgvw-BEshmQJp3kFdSMLGncfQ@mail.gmail.com \
    --to=markus.mottl@gmail.com \
    --cc=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=dra-news@metastack.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;
as well as URLs for NNTP newsgroup(s).