[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] using configure options to specifiy mandir, docdir and others



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?


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.