From: Anastasia Gornostaeva <ermine@ermine.pp.ru>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: oasis
Date: Sat, 27 Nov 2010 16:10:05 +0300 [thread overview]
Message-ID: <20101127131005.GA2407@ermine.home> (raw)
In-Reply-To: <slrnif1mrm.r67.sylvain@gallu.homelinux.org>
On Sat, Nov 27, 2010 at 10:20:38AM +0000, Sylvain Le Gall wrote:
> Hi,
>
> On 26-11-2010, Anastasia Gornostaeva <ermine@ermine.pp.ru> wrote:
> > Hello.
> >
> > How can I substitute in setup.ml (not in _oasis file) values for
> > CCOpt and CCLib fields? I think it is better to substitute them from
> > setup.data, if I could to put proper values to setup.data.
> > For example:
> > CCOpt: $freetype_ccopt
> > and put to setup.data output of `freetype-config --clib` for field
> > freetype_ccopt.
>
> As I answer you in private: there will be pkg-config support in 0.3.0.
> This will solve this issue, at least.
> (e.g. you will be able to define:
> BuildDepends: freetype2 (pkg-config), oUnit, ...)
Sorry, but i didnt receive your mail..
And pkg-config probably is not best solution on bsd and macosx systems because
it does not guarante nothing.
The best (and common) solution is CFLAGS and LIBS env variables. :-)
Or this pkg-config will allow custom paths for those C librares that do not
depend on pkg-config at concrete systems?
[...]
> > I need a way to substitute paths.
> >
>
> A last solution, you can apply right now, is to override this call:
> let () = setup ();;
> (last line of setup.ml)
>
> by
>
> let f pkg =
> (* Call freetype-config and add flags where
> needed in pkg
> *)
> ...
>
> let () = BaseSetup.setup (f setup_t);;
Interesting way. Thanks, I'll ckeck it right how.
Thanks.
ermine
next prev parent reply other threads:[~2010-11-27 13:10 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 ` Anastasia Gornostaeva [this message]
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
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=20101127131005.GA2407@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