File: INSTALLING

package info (click to toggle)
unixcw 3.0.2-1
  • links: PTS
  • area: main
  • in suites: wheezy
  • size: 2,056 kB
  • sloc: ansic: 7,579; cpp: 1,477; sh: 549; makefile: 416; awk: 224
file content (77 lines) | stat: -rw-r--r-- 2,881 bytes parent folder | download
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
72
73
74
75
76
77

The source code for UnixCW version 3.0 comes with a 'configure' file.  Its job
is to try and decide which features your system offers, and then configure
UnixCW the best way it can for these features.

At minimum, you will need a set of sound card definitions (usually in the file
soundcard.h) and perhaps also a KIOCSOUND console sound ioctl available on your
system; these are used to build the CW library.  Note that it's not necessary
for the system doing the build to actually have a sound card, nor for that
matter, a working console speaker, but you will need the definitions from
various header files.  Of course, you will need a sound card or console speaker
if you want to run any of the programs once they are built.

cwcp:
If you have a Curses (ncurses) library, UnixCW will build 'cwcp'.

xcwcp:
If you have a Qt library, version 4.0 or later, and a C++ compiler, UnixCW
will build 'xcwcp'. 'configure' script will try to resolve all dependencies
needed to build QT4 application without using QT-specific build tools.
If the script fails at detecting 'moc' executable or include files for QT4,
you may have to set the environment variable QT4DIR (if not already set)
to indicate the Qt library directory on your system. On Debian it would be:

    export QT4DIR=/usr/share/qt4

The configure script will then look for the Qt4 'moc' utility on either your
current $PATH or in $QT4DIR/bin.

UnixCW may port to other platforms, but the primary target systems on which it
should "just build", perhaps with a bit of tweaking as shown above with
environment variables, are:

    o Linux
    o FreeBSD


To build the CW library and the UnixCW applications, you should be able to type
the following commands in the directory where you unpacked the source code:

    ./configure
    make all

'configure' will tell you of any problems with missing features on your system.
If you lack a Qt library, it will omit building 'xcwcp'.  If you lack a Curses
library, it will omit building 'cwcp'.  The other components should still
build, however.


Assuming the 'make all' succeeded, you can now install the programs with

    make install

By default, this will install everything under /usr/local.  You would probably
want to be 'root' to do this, otherwise you may not have the permissions to
write files to the installation directory.

Note that it is not necessary to install the programs in order to run them.
You should be able to run any of them in the directories in which they built
themselves.


To uninstall the programs, use

    make uninstall

with the same user/permissions as you used for installing.  To clean out the
directory for a rebuild, use

    make distclean

If you have autoconf and the other auto* tools installed on your system, you
can regenerate the configure file, if you like, from configure.in, with

    make maintainer-clean
    sh autogen.sh