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 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134
|
LifeLines Source Release, Version 3.0.9post
http://lifelines.sourceforge.net
-------------------------------------------------------------------------
********************************
Contents:
1. General (UNIX) installation
2. Platform specific notes
2a) Microsoft Windows
2b) cygwin
2c) gcc 2.7.2.1
2d) curses
2e) Mac OS X
********************************
******************************
1. General (UNIX) installation
******************************
This is the source distribution of the LifeLines system, a genealogy
software system.
LifeLines should compile correctly using GNU gcc or any native C compiler.
It also will build using the Cygnus tools on Windows (but see note in the
platform notes section below).
To build and install LifeLines, do the following:
./configure (if that does't work, try 'sh ./configure')
make
make install
This will generate Makefiles suitable for your platform and then build
and install the LifeLines programs. You will end up with the following
executables (installed in various places, depending on your platform):
llines -- main LifeLines system program
btedit -- general purpose btree edit program
dbverify -- checks a LifeLines database for problems
llines is the main LifeLines program.
dverify can be used to verify the correctness of a LifeLines database.
This is handy if you're storing databases on floppies, or just for
peace of mind.
btedit is a administration tool used for unmangling mangled databases,
and is extremely powerful. You should only use this program under the
expert guidance of a LifeLines developer.
**************************
2. Platform specific notes
**************************
*********************
2a) Microsoft Windows
*********************
For installing the binary distribution on MS-Windows, refer to the
file Install.LifeLines.Windows.txt included in that distribution
(& also included in the docs subdirectory of the source
distributions).
For compiling from source on MS-Windows, if using cygwin, refer to
the General (UNIX) instruction above (and see also the cygwin note
below). If using MS Visual C++, you may use the project files
included in the subdirectories beneath /win32/msvc6 (which are
currently used by Perry to generate the binaries in the MS-Windows
binary distribution).
**********
2b) Cygwin
**********
Cygwin is a UNIX environment for MS-Windows.
http://sources.redhat.com/cygwin
The lines around the boxes in the lifelines curses GUI use OEM
box characters, and so only display correctly with this setting:
export CYGWIN=codepage:oem
This of course affects the console code page. If all your data is
ASCII, this solution may work fine for you. Otherwise, you may
invoke llines with the -z switch to suppress curses graphics, and
use primitive ASCII graphics. This is not particularly attractive,
but is usable. Suggestions are welcome.
Note that the -z commandline switch was added after the 3.0.9
release.
***************
2c) gcc 2.7.2.1
***************
gcc 2.7.2.1 does not understand -Wreturn-type, so this
must be removed from configure and from CFLAGS in
interp/Makefile* files. This must be done before configuring,
because it causes configure tests to fail spuriously.
(Jan, 2002)
**********
2d) curses
**********
Compiling with curses (lacking ncurses) on a BSDI 3.1 box,
I had to add
-ltermcap
to the LIBS line in liflines/Makefile. (The symptom was
"unknown symbol... _tputs.)
However, I wound up core dumping at run-time, so I don't know
what is going on.
(Perry, Jan, 2002)
************
2e) Mac OS X
************
Please see the following page about LifeLines on Mac OS X:
http://homepage.mac.com/shrubbery/LifeLines
(which is also available via the Apple downloads site and Stepwise.)
This page offers both precompiled binaries and instructions for
compilation.
NB: Because the gnu tests for platform don't recognize Darwin,
configure requires an argument, eg "./configure ppc". There is no
specific code needed for Darwin; this is just to avoid the macros
getting angry at the unknown output from "uname -a".
|