From: Chet Murthy <murthy.chet@gmail.com>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] OASIS question: how does one set variables ?
Date: Mon, 6 Jun 2016 19:59:06 -0700 [thread overview]
Message-ID: <CA++P_gcRMG1xp_s-1d3-p9iVfMZNXn+mLSe-Cn2wVh5D_s=jew@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
I'd like to avoid as much as possible the preservation of generated files,
when using oasis. _tags isn't a problem (likewise Makefile) since they
have a clear separation between what is customized, and what is
oasis-generated. But setup.data does not have such a separation.
But I'd like to change things like "bindir", and probably other things
too. Is there a way to specify such customizations in _oasis?
Thanks,
--chet--
[-- Attachment #2: Type: text/html, Size: 565 bytes --]
next reply other threads:[~2016-06-07 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 2:59 Chet Murthy [this message]
2016-06-07 12:40 ` [Caml-list] How to include files dynamically Nicolas Ratier
2016-06-07 12:48 ` Sébastien Hinderer
2016-06-08 4:16 ` Mark Bradley
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='CA++P_gcRMG1xp_s-1d3-p9iVfMZNXn+mLSe-Cn2wVh5D_s=jew@mail.gmail.com' \
--to=murthy.chet@gmail.com \
--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).