Re: [Xen-devel] [PATCH v8 3/6] autoconf: xen: move standard path variables to config/Paths.mk.in

[Julien Grall <julien.grall@xxxxxxxxxx>]

Hi,

On 07/26/2014 03:14 AM, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@xxxxxxxx>
> 
> This moves all generic path variables to a new the config/Paths.mk.in
> input source file to be processed at configure time, tons of files use
> these so this just share them. This also paves the way to let us
> easily dynamically configure these with autoconf, for now we leave the
> same presets as was present before.
> 
> This work was prompted by looking for an autoconf way to do
> replacements for the hotplug global file, while at it I realized
> that a few other files use the same variables and have in places
> around the tree the same constructs for generating their own
> files. This makes use of the old buildmakevars2file() but generalizes
> the definition of the paths at configure time and spreads the
> new definitions out throughout the build system.
> 
> This has no impact on building the hypervisor and extras/mini-os,
> you do not need to, and are not expected to, run configure to build
> those targets.
> 
> While at it lets add some documentation on the for the two files on
> the source file, we can expand further details on the wiki [0].
> 
> [0] 
> http://wiki.xen.org/wiki/Category:Host_Configuration#System_wide_xen_configuration

With this patch applied on xen tree (see commit 54f2891), the libraries will 
always be
copied in /usr/local/lib even if --prefix=/usr is specified to the configure.

It's a bit annoying as I used this options daily to build Xen and we have test 
suite relying
on this option.

Here my config/Paths.mk generated:

# Xen system configuration
# ========================
#
# Xen uses a set of variables for system configuration and at build time,
# because of this these variables are defined on one master input source file
# and is generated after running ./configure. The master source is located
# on the xen source tree at under config/Paths.mk.in and it is used to
# generate shell or header files by the build system upon demand through the
# use of the helper makefile helper buildmakevars2file().
#
# For more documentation you can refer to the wiki:
#
# 
http://wiki.xen.org/wiki/Category:Host_Configuration#System_wide_xen_configuration

SBINDIR                  := /usr/sbin
BINDIR                   := /usr/bin
LIBEXEC                  := /usr/lib/xen/bin

SHAREDIR                 := /usr/share
LIBDIR                   := /usr/local/lib

XEN_RUN_DIR              := /var/run/xen
XEN_LOG_DIR              := /var/log/xen
XEN_LIB_STORED           := /var/lib/xenstored

CONFIG_DIR               := /etc
XEN_LOCK_DIR             := /var/lock
XEN_PAGING_DIR           := /var/lib/xen/xenpaging

PRIVATE_PREFIX           := /usr/local/lib/xen
PRIVATE_PREFIX           := /usr/local/lib/xen
PRIVATE_BINDIR           := /usr/local/lib/xen/bin

XENFIRMWAREDIR           := /usr/lib/xen/boot

XEN_CONFIG_DIR           := /etc/xen
XEN_SCRIPT_DIR           := /etc/xen/scripts

Regards,

-- 
Julien Grall

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