From: Roger Pau Monne <roger.pau@citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: using configure options to specifiy mandir, docdir and others
Date: Mon, 11 Jun 2012 13:20:00 +0100 [thread overview]
Message-ID: <4FD5E270.4000305@citrix.com> (raw)
In-Reply-To: <20120611114029.GA10576@aepfle.de>
Olaf Hering wrote:
> I'm currently preparing a patch to install the documentation files
> referenced in the various man pages. While doing that I tried to add
> the config options from configure into config/Tools.mk. But this fails
> because @docdir@ expands to something like
> ${datadir}/doc/$PACKAGE_TARNAME instead of something useful. I see
Why don't you export datadir also in Tools.mk if needed?
http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Installation-Directory-Variables.html
> DOCDIR and other variables are already hardcoded in Config.mk, and even
> PYTHON is listed in Config.mk instead of Tools.mk.
PYTHON is in Config.mk because it is needed to build the hypervisor, and
we agreed that building the hypervisor doesn't require the user to run
the configure script.
Other paths should be in Config/Tools.mk or Config/Docs.mk (don't really
know if we want to split this into two different files).
> Is there way to use the values passed to configure instead of hardcoding
> them into Config.mk?
prev parent reply other threads:[~2012-06-11 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 11:40 using configure options to specifiy mandir, docdir and others Olaf Hering
2012-06-11 12:20 ` Roger Pau Monne [this message]
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=4FD5E270.4000305@citrix.com \
--to=roger.pau@citrix.com \
--cc=olaf@aepfle.de \
--cc=xen-devel@lists.xen.org \
/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).