From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roger Pau Monne Subject: Re: using configure options to specifiy mandir, docdir and others Date: Mon, 11 Jun 2012 13:20:00 +0100 Message-ID: <4FD5E270.4000305@citrix.com> References: <20120611114029.GA10576@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120611114029.GA10576@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org 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?