mirror of
https://github.com/checkpoint-restore/criu.git
synced 2026-01-23 02:14:37 +00:00
DESTDIR is mostly used by packagers (such as from rpm spec or deb rules), or just to try installation, and normally should be left unset/empty. Setting it to / looks weird to me. Besides, by leaving it empty we are making sure everything works if DESTDIR is not set. Fix INSTALL.md accordingly. travis-ci: success for Makefile.install: DESTDIR should be empty CC: Cyrill Gorcunov <gorcunov@openvz.org> Signed-off-by: Kir Kolyshkin <kir@openvz.org> Signed-off-by: Pavel Emelyanov <xemul@virtuozzo.com>
1.3 KiB
1.3 KiB
Installing CRIU from source code
Once CRIU is built one can easily setup the complete CRIU package (which includes executable itself, CRIT tool, libraries, manual and etc) simply typing
make install
this command accepts the following variables:
- DESTDIR, to specify global root where all components will be placed under (empty by default);
- PREFIX, to specify additional prefix for path of every component installed (
/usr/localby default); - BINDIR, to specify where to put CRIT tool (
$(PREFIX)/binby default); - SBINDIR, to specify where to put CRIU executable (
$(PREFIX)/sbinby default); - MANDIR, to specify directory for manual pages (
$(PREFIX)/share/manby default); - SYSTEMDUNITDIR, to specify place where systemd units are living (
$(PREFIX)/lib/systemd/systemby default); - LIBDIR, to specify directory where to put libraries (
$(PREFIX)/libby default).
Thus one can type
make DESTDIR=/some/new/place install
and get everything installed under /some/new/place.
Uninstalling CRIU
To clean up previously installed CRIU instance one can type
make uninstall
and everything should be removed. Note though that if some variable (DESTDIR, BINDIR and such) has been used during installation procedure, the same must be passed with uninstall action.