caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anastasia Gornostaeva <ermine@ermine.pp.ru>
To: Sylvain Le Gall <sylvain@le-gall.net>, caml-list@inria.fr
Subject: Re: [Caml-list] Re: oasis
Date: Mon, 29 Nov 2010 22:46:22 +0300	[thread overview]
Message-ID: <20101129194622.GA41946@ermine.home> (raw)
In-Reply-To: <slrnif53le.r67.sylvain@gallu.homelinux.org>

On Sun, Nov 28, 2010 at 05:17:35PM +0000, Sylvain Le Gall wrote:

> My current state about this solution is:
> - defines BuildDepends: freetype2 (pkg-config), to make clear that there
>   is a C build-depends
> - allow to override the defined variable freetype2_cflags and
>   freetype2_libs. If they are both defined by user, don't even call
>   pkg-config for this package

There should be three variants: pkg-config, OS-based userspace policy 
(/usr/include vs. /usr/local/include) and user-defined one.

> Here is a new proposal about this:
> - use a PostConfigureCommand to invoke a shell script freetype2.sh
> - in freetype2.sh invoke freetype-config and output flags in setup.data
>   using "echo 'freetype2_cflags = "$output"' >> setup.data' and
>   "echo 'freetype2_libs = "$output"' >> setup.data' 
> - add in _tags a "src/toto.cma: pkg_config_freetype2" 
> - add in myocamlbuild.ml a "tag [pkg_config_freetyp2; compile; ocaml] &
>   [... (* load the content of freetyp2_cflags *) ... ]"
> 
> This is not simple but this is probably what I will do for the support
> of C libraries in 0.3.0.

But it is the best solution now and partially works for me.
And please make the functions that loads setup.data and var_get data from it 
to be public. Right now I attempt to play with your code in myocamlbuild.ml 
and re-use it in my piece at bottom of the file.
I'm always ready to test/use oasis from darcs when you put there something new.

ermine

> 
> Regards,
> Sylvain Le Gall
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs


  reply	other threads:[~2010-11-29 19:46 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       ` Anastasia Gornostaeva [this message]
2010-11-29 20:52         ` [Caml-list] oasis 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=20101129194622.GA41946@ermine.home \
    --to=ermine@ermine.pp.ru \
    --cc=caml-list@inria.fr \
    --cc=sylvain@le-gall.net \
    /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).