From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <edwin+ml-ocaml@etorok.net>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105])
	by sympa.inria.fr (Postfix) with ESMTPS id E4E157F2AA
	for <caml-list@sympa.inria.fr>; Sat, 15 Dec 2012 17:59:41 +0100 (CET)
Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  edwin+ml-ocaml@etorok.net) identity=pra;
  client-ip=176.9.138.55;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="edwin+ml-ocaml@etorok.net";
  x-sender="edwin+ml-ocaml@etorok.net";
  x-conformance=sidf_compatible
Received-SPF: Pass (mail4-smtp-sop.national.inria.fr: domain of
  edwin+ml-ocaml@etorok.net designates 176.9.138.55 as
  permitted sender) identity=mailfrom; client-ip=176.9.138.55;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="edwin+ml-ocaml@etorok.net";
  x-sender="edwin+ml-ocaml@etorok.net";
  x-conformance=sidf_compatible; x-record-type="v=spf1"
Received-SPF: Pass (mail4-smtp-sop.national.inria.fr: domain of
  postmaster@mail.etorok.net designates 176.9.138.55 as
  permitted sender) identity=helo; client-ip=176.9.138.55;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="edwin+ml-ocaml@etorok.net";
  x-sender="postmaster@mail.etorok.net";
  x-conformance=sidf_compatible; x-record-type="v=spf1"
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0HAEmrzFCwCYo3/2dsb2JhbABFgmxcgnO4FxZzgh4BAQUjHQEBNgIPCxgCAgUWCwICCQMCAQIBRRMIAogQA6d8cINKAQWOYAaBIos7BYEVghaBE5YMkEiCdQ
X-IronPort-AV: E=Sophos;i="4.84,291,1355094000"; 
   d="scan'208";a="165946218"
Received: from mail.etorok.net ([176.9.138.55])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 15 Dec 2012 17:59:40 +0100
Received: from [IPv6:2a02:2f02:1022:618f:1e6f:65ff:fe23:db0d] (unknown [IPv6:2a02:2f02:1022:618f:1e6f:65ff:fe23:db0d])
	by mail.etorok.net (Postfix) with ESMTPSA id A0A0A46AE
	for <caml-list@inria.fr>; Sat, 15 Dec 2012 17:59:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=etorok.net;
	s=MAILOUT; t=1355590775;
	bh=15EDiwexv1o6L6J30Dl0F0bV4IY8YWs//ED7zwOg1HA=;
	h=Message-ID:Date:From:MIME-Version:To:Subject:References:
	 In-Reply-To:Content-Type:Content-Transfer-Encoding;
	b=lkH/EDEDc8A3j+TH3FZbIH27TJTQZDtS49WHO5xQpx5TGzWxGGA0sKlRjxWlZ5tL9
	 Asrr+T2uc935VappkIzamN9rK47FS2j/8RveCYpsE3B9LZOpkV2k46wRjQiPPFfNpu
	 gJlfPwCUCS94i0GGNLIaexXvlYu3CXrZRi7MY2xM=
Message-ID: <50CCAC75.8010701@etorok.net>
Date: Sat, 15 Dec 2012 18:59:33 +0200
From: =?UTF-8?B?VMO2csO2ayBFZHdpbg==?= <edwin+ml-ocaml@etorok.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: caml-list@inria.fr
References: <1355587355.56246.YahooMailNeo@web120405.mail.ne1.yahoo.com>
In-Reply-To: <1355587355.56246.YahooMailNeo@web120405.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.97.6 at mail
X-Virus-Status: Clean
Subject: Re: [Caml-list] OASIS and conditional compilation

On 12/15/2012 06:02 PM, Dario Teixeira wrote:
> Hi,
> 
> I've come across a perplexing issue with OASIS.  I'm not sure if this is
> just a bug or if I'm trying to push the tool beyond its design parameters.
> 
> PG'OCaml can be compiled against either Batteries or ExtLib (the latter
> mostly for legacy compatibility). To allow the harmonious coexistence of
> the two options in the same system, the build system should allow for
> the compilation of one or the two versions of the library side by side.
> In OASIS-speak (I'm using version 0.3):
> 
>   Flag "batteries"
>     Description: Link PG'OCaml against Batteries
>     Default: true
> 
>   Flag "extlib"
>     Description: Link PG'OCaml against ExtLib
>     Default: true
> 
>   Library "pgocaml_batteries"
>     Build$:               flag(batteries)
>     Install$:             flag(batteries)
>     Path:                 src
>     Modules:              PGOCaml, PGOCaml_generic
>     BuildDepends:         unix, calendar, csv, pcre, batteries, camlp4.macro
>     ByteOpt+:             -ppopt -DUSE_BATTERIES
>     NativeOpt+:           -ppopt -DUSE_BATTERIES

I think it simply adds these to the tags file, and since its the same module name
in both cases it'll get built with those flags even when batteries is disabled.

--Edwin