File: INSTALL

package info (click to toggle)
xlunzip 0.4-3
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster
  • size: 276 kB
  • sloc: ansic: 2,063; sh: 430; makefile: 109
file content (71 lines) | stat: -rw-r--r-- 2,130 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
Requirements
------------
You will need a C compiler.
I use gcc 5.3.0 and 4.1.2, but the code should compile with any
standards compliant compiler.
Gcc is available at http://gcc.gnu.org.


Procedure
---------
1. Unpack the archive if you have not done so already:

	tar -xf xlunzip[version].tar.lz
or
	lzip -cd xlunzip[version].tar.lz | tar -xf -

This creates the directory ./xlunzip[version] containing the source from
the main archive.

2. Change to xlunzip directory and run configure.
   (Try 'configure --help' for usage instructions).

	cd xlunzip[version]
	./configure

3. Run make.

	make

4. Optionally, type 'make check' to run the tests that come with xlunzip.

5. Type 'make install' to install the program and any data files and
   documentation.

   Or type 'make install-compress', which additionally compresses the
   man page after installation. (Installing compressed docs may become
   the default in the future).

   You can install only the program or the man page by typing 'make
   install-bin' or 'make install-man' respectively.

   Instead of 'make install', you can type 'make install-as-lzip' to
   install the program and any data files and documentation, and link
   the program to the name 'lzip'.

If you are compiling on MinGW, replace step 3 with:

	make CFLAGS='-Wall -W -O2 -D __USE_MINGW_ANSI_STDIO'


Another way
-----------
You can also compile xlunzip into a separate directory.
To do this, you must use a version of 'make' that supports the 'VPATH'
variable, such as GNU 'make'. 'cd' to the directory where you want the
object files and executables to go and run the 'configure' script.
'configure' automatically checks for the source code in '.', in '..' and
in the directory that 'configure' is in.

'configure' recognizes the option '--srcdir=DIR' to control where to
look for the sources. Usually 'configure' can determine that directory
automatically.

After running 'configure', you can run 'make' and 'make install' as
explained above.


Copyright (C) 2016-2018 Antonio Diaz Diaz.

This file is free documentation: you have unlimited permission to copy,
distribute and modify it.