caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anastasia Gornostaeva <ermine@ermine.pp.ru>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: oasis
Date: Tue, 30 Nov 2010 00:19:56 +0300	[thread overview]
Message-ID: <20101129211956.GB42454@ermine.home> (raw)
In-Reply-To: <20101129205220.GB5831@yocto.gallu.homelinux.org>

On Mon, Nov 29, 2010 at 09:52:20PM +0100, Sylvain Le Gall wrote:

> > There should be three variants: pkg-config, OS-based userspace policy 
> > (/usr/include vs. /usr/local/include) and user-defined one.
> > 
> 
> I think the pkg-config is the starting point, it also defines the prefix
> of the setup.data variable that we will use.

> For you OS-based detection, I can propose a header(XXX), lib(XXX). This
> will be cumulative (i.e. you can define several header and lib).
> 
> Example:
> BuildDepends: 
>   freetype2(pkg-config, header(freetype/freetype.h), lib(freetype), >= 2.0.4),
>   oUnit
> 
> The headers and libs fields are extra methods. If you define
> them, we will try to find a set of -Idirs that help to find the
> matching headers or a -Ldirs to find the matching libs. 
> 
> We will only do a detection using Sys.file_exists (i.e. don't try to
> link or anything similar). 
> 
> The detection method start with pkg-config and if it fails goes to
> headers/libs.

Excellent. I agree. I hope that default dirs for searching using 
Filename.exists will be defined somewhere not especaiily deeply.

[..]

ermine


      reply	other threads:[~2010-11-29 21:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26 18:38 oasis Anastasia Gornostaeva
2010-11-27 10:20 ` oasis Sylvain Le Gall
2010-11-27 13:10   ` [Caml-list] oasis Anastasia Gornostaeva
2010-11-28 17:17     ` oasis Sylvain Le Gall
2010-11-29 19:46       ` [Caml-list] oasis Anastasia Gornostaeva
2010-11-29 20:52         ` Sylvain Le Gall
2010-11-29 21:19           ` Anastasia Gornostaeva [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=20101129211956.GB42454@ermine.home \
    --to=ermine@ermine.pp.ru \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).