+++ /dev/null
-# Suggested list of file renames.
-#
-# File renames don't normally go into patches because they make
-# the patches much harder to read, so list them here instead.
-
-# Clearer naming scheme after Xen-unified patch went in.
-src/xen_internal.c src/xen_internal_hv.c
-src/xen_internal.h src/xen_internal_hv.h
-src/proxy_internal.c src/xen_internal_proxy.c
-src/proxy_internal.h src/xen_internal_proxy.h
-src/xend_internal.c src/xen_internal_xend.c
-src/xend_internal.h src/xen_internal_xend.h
-src/xm_internal.c src/xen_internal_inactive.c
-src/xm_internal.h src/xen_internal_inactive.h
-src/xs_internal.c src/xen_internal_xenstore.c
-src/xs_internal.h src/xen_internal_xenstore.h
-src/xen_unified.c src/xen_internal.c
-src/xen_unified.h src/xen_internal.h
-
-# Test driver should really be called test_internal.
-src/test.c src/test_internal.c
-src/test.h src/test_internal.h
-
-# This would be better:
-src/*_internal*.c src/*_driver*.c
-src/*_internal*.h src/*_driver*.h
-
-# Qemud is now the qemud + remote driver.
-qemud/protocol.x qemud/qemud_protocol.x
-qemud/* remote/*
+++ /dev/null
-
- Why libxen:
- -----------
-
-
- The main goals of the library is to provide an stable API abstracting
-the underlying acual implementation of the hypervisor calls.
-
-1/ Stable API:
- by isolating the data structures and entry points used at the low
- level Xen Hypervisor interfaces, allowing evolution of said interface
- over time without breaking the application visible API and ABI
-
-2/ Abstraction:
- by providing at the C level simplified concept exposed only as opaque
- structure for the hypervisor connection, domains and other kind of
- objects which may be needed in the future. It must also provide
- a set of higher level function calls simplifying the developement
- of applications using the supervisor.
-
-3/ Maintainability and openness:
- All data structures and entry points must be fully documented, all
- changes will be driven in an open fashion based on a publicly archived
- mailing-list allowing peer-review before changes will be introduced.
- Tools and regression tests will be implemented and shipped as part of the
- releases of the library.
-
-Daniel Veillard <veillard@redhat.com>
+++ /dev/null
-#!/bin/sh
-
-mode=libtool
-cfiles=""
-ofiles=""
-afiles=""
-
-wantnext=0
-for v in "$@"
-do
- case $v
- in
- --mode=compile)
- mode=CC
- ;;
- --mode=link)
- mode=LD
- ;;
- esac
-
- case $v
- in
- *.c)
- cfiles="$cfiles $v"
- ;;
- *.o)
- if [ "$mode" = "LD" -o "$wantnext" = "1" ]; then
- ofiles="$ofiles $v"
- fi
- ;;
- *.lo)
- if [ "$mode" = "LD" -o "$wantnext" = "1" ]; then
- ofiles="$ofiles $v"
- fi
- ;;
- esac
-
- if [ "$mode" = "LD" -a "$wantnext" = "1" ]; then
- afiles="$afiles $v"
- fi
-
- if [ "$v" = "-o" ]; then
- wantnext=1
- else
- wantnext=0
- fi
-done
-
-args=""
-test -n "$afiles" && args="$args -o$afiles"
-test -n "$ofiles" -a "$mode" = "CC" && args="$args -o"
-test -n "$ofiles" && args="$args$ofiles"
-test -n "$cfiles" && args="$args$cfiles"
-
-echo "($mode)$args"
-
-here=`dirname $0`
-exec $here/libtool --silent "$@"