From: "Török Edwin" <edwin+ml-ocaml@etorok.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OASIS and conditional compilation
Date: Sat, 15 Dec 2012 18:59:33 +0200 [thread overview]
Message-ID: <50CCAC75.8010701@etorok.net> (raw)
In-Reply-To: <1355587355.56246.YahooMailNeo@web120405.mail.ne1.yahoo.com>
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
next prev parent reply other threads:[~2012-12-15 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 16:02 Dario Teixeira
2012-12-15 16:17 ` Wojciech Meyer
2012-12-15 16:56 ` Dario Teixeira
2012-12-15 17:23 ` Sylvain Le Gall
2012-12-15 18:25 ` Dario Teixeira
2012-12-15 16:59 ` Török Edwin [this message]
2012-12-15 18:31 ` Dario Teixeira
2012-12-16 1:13 ` Jacques-Pascal Deplaix
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=50CCAC75.8010701@etorok.net \
--to=edwin+ml-ocaml@etorok.net \
--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).