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
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
<HEAD><style> A { color:black }</style>
<!-- hennerik CVSweb $Revision: 1.93 $ -->
<TITLE>code/nel/INSTALL - view - 1.15</TITLE></HEAD>
<BODY BGCOLOR="#eeeeee">
<table width="100%" border=0 cellspacing=0 cellpadding=1 bgcolor="#aaaaaa"><tr valign=bottom><td><a href="INSTALL?sortby=log"><IMG SRC="/inc/img/picto-up.gif" ALT="[BACK]" BORDER="0" WIDTH="14" HEIGHT="13"></a> <b>Return to <A HREF="INSTALL?sortby=log">INSTALL</A>
CVS log</b> <IMG SRC="/inc/img/picto-news.gif" ALT="[TXT]" BORDER="0" WIDTH="13" HEIGHT="15"></td><td align=right><IMG SRC="/inc/img/picto-dir.gif" ALT="[DIR]" BORDER="0" WIDTH="15" HEIGHT="13"> <b>Up to <a href="/cvs/cvsweb.cgi/?sortby=log">Nevrax</a> / <a href="/cvs/cvsweb.cgi/code/?sortby=log">code</a> / <a href="/cvs/cvsweb.cgi/code/nel/?sortby=log">nel</a></b></td></tr></table><HR noshade><table width="100%"><tr><td bgcolor="#ffffff">File: <a href="/cvs/cvsweb.cgi/?sortby=log">Nevrax</a> / <a href="/cvs/cvsweb.cgi/code/?sortby=log">code</a> / <a href="/cvs/cvsweb.cgi/code/nel/?sortby=log">nel</a> / <a href="/cvs/cvsweb.cgi/code/nel/INSTALL?sortby=log">INSTALL</a> (<A HREF="/cvs/cvsweb.cgi/~checkout~/code/nel/INSTALL?rev=1.15&sortby=log" target="cvs_checkout" onClick="window.open('/cvs/cvsweb.cgi/~checkout~/code/nel/INSTALL?rev=1.15','cvs_checkout','resizeable,scrollbars');"><b>download</b></A>)<BR>
Revision <B>1.15</B>, <i>Tue Apr 10 13:44:50 2001 UTC</i> (15 months ago) by <i>loic_at_senga.org</i>
<BR>Branch: <b>MAIN</b>
<BR>Changes since <b>1.14: +6 -9
lines</b><PRE>
ADDED configure(s) arguments --with-debug and --without-debug to change
gcc arguments (-g -O -O3 etc ...).
</PRE>
</td></tr></table><HR noshade><PRE>
If you find any bugs use the Nevrax Bug Tracking System :
<URL:<A HREF="/bugs/">/bugs/</A>>
If you need any help contact us on the NeL mailing-list :
<URL:<A HREF="/mail/">/mail/</A>>
Requirements
============
The NeL library need the following libraries :
- STLPort 4.0 <URL:<A HREF="http://www.stlport.org/">http://www.stlport.org/</A>>
- FreeType 2 <URL:<A HREF="http://freetype.sourceforge.net/">http://freetype.sourceforge.net/</A>>
- Python 1.5 <URL:<A HREF="http://www.python.org/">http://www.python.org/</A>>
STLPort need to be compiled. NeL is using the SGI iostreams and it require
the STLPort compilation and a linking of NeL with the STLPort library.
On a GNU/Linux platform you will need the following libraries and
softwares :
- Autoconf <URL:<A HREF="http://www.gnu.org/software/autoconf/autoconf.html">http://www.gnu.org/software/autoconf/autoconf.html</A>>
- Automake <URL:<A HREF="http://www.gnu.org/software/automake/automake.html">http://www.gnu.org/software/automake/automake.html</A>>
- Libtool <URL:<A HREF="http://www.gnu.org/software/libtool/libtool.html">http://www.gnu.org/software/libtool/libtool.html</A>>
- Lex / Flex <URL:<A HREF="http://www.gnu.org/software/flex/flex.html">http://www.gnu.org/software/flex/flex.html</A>>
- Yacc / Bison <URL:<A HREF="http://www.gnu.org/software/bison/bison.html">http://www.gnu.org/software/bison/bison.html</A>>
- Mesa 3.3 <URL:<A HREF="http://www.mesa3d.org/">http://www.mesa3d.org/</A>>
On some OpenGL implementations, you migth have some troubles, coming from
the <GL/glext.h> file, to get NeL to compile. This file could be missing
or not up to date. You will find the latest version of this file on SGI's
website :
- glext.h <URL:<A HREF="http://oss.sgi.com/projects/ogl-sample/ABI/glext.h">http://oss.sgi.com/projects/ogl-sample/ABI/glext.h</A>>
Most of our documentation is done using Doxygen, so you might need it
to read our prose and our code documentation. If you want have nice
graphs like dependency graphs, collaboration diagrams, or graphical
class hierarchy graphs you will need Graphviz :
- Doxygen <URL:<A HREF="http://www.stack.nl/~dimitri/doxygen/">http://www.stack.nl/~dimitri/doxygen/</A>>
- Graphviz <URL:<A HREF="http://www.research.att.com/sw/tools/graphviz/">http://www.research.att.com/sw/tools/graphviz/</A>>
Most of these softwares should be already installed on your system or
provided on your installation disk.
The given sofware or library version numbers are the ones that we are
using. We don't know if it working with other (older or more recent)
versions of these softwares or libraries. You are welcome to help us
to define more precisely these informations ;-)
Compilation
===========
1. Windows compilation
----------------------
The compilation on Windows has been done only with Visual C++ 6.0 SP4.
You first need to compile STLport and FreeType libraries. It's a quite
long compilation process, and you should carefully read these libraries
documentation (at least the README and INSTALL files) before compiling
and installing them.
STLport Compilation :
- Open a Dos window and go in the STLPort's src directory.
- Rename or copy the "vc6-unicode.mak" to "Makefile".
- Execute `nmake clean all` followed by `nmake install`.
FreeType compilation, by using GNU Make :
- You need to intall GNU make and to place it in the PATH.
<URL:<A HREF="http://ftpsearch.lycos.com/swadv/AdvResults.asp?query=gnumake-win32">http://ftpsearch.lycos.com/swadv/AdvResults.asp?query=gnumake-win32</A>>
- Open a Dos window and go in the FreeType's directory.
- Execute `make setup visualc' followed by `make`.
FreeType compilation, by using an IDE :
- Compile every (base and optionnal) library components listed
at the end of the FreeType's INSTALL file.
Set up Visual C++ to find the STLPort and FreeType libraries. This
is done in the [Tools -> Options -> Directories] menu :
- Add the STLPort include directory to the "Library Files" category.
The STLPort include *must* be inserted before the microsoft one or
the compiler will take microsoft STL instead of STLPort STL.
(use the arrow button to put the STLPort include at the top)
ex: D:/stlport-4.0/stlport
- Add the STLPort library directory to the "Library Files" category.
ex: D:/stlport-4.0/lib
- Add the FreeType include directory to the "Include Files" category.
ex: D:/freetype-2.0/include
- Add the FreeType library directory to the "Library Files" category.
ex: D:/freetype-2.0/obj
Open the workspace file "nel.dsw" (in the menu [File -> Workspace]).
Setup Visual C++ to find the NeL include and library files :
- Add the NEL include directory to the "Library Files" category.
ex: D:/test/code/nel/include
- Add the STLPort library directory to the "Library Files" category.
ex: D:/test/code/nel/lib
2. GNU/Linux compilation
------------------------
In the NeL directory do :
In the case (ex: after a cvs checkout) that you need to rebuild the
"configure" script and/or the "Makefile.in" files, execute the
"bootstrap" script in the NeL directory :
% ./bootstrap
% ./configure --with-stlport=<Path_to_the_stlport_headers_files> \
--with-python=<Path_to_the_python_headers_files>
% make
The "configure" script must be call with the "--with-stlport" and
"--with-python" options.
The option "--with-stlport" allow to override the default STL headers
and the option "--with-python" tell to the configuration script, where
to find the Python headers files.
You migth need to specify the FreeType 2 installation prefix by using
the "--with-freetype" argument (ex: "/usr/local" will look for the
header files in "/usr/local/include" and the library files in the
"/usr/local/lid/ directory).
To pass additional arguments to the C++ compiler, use the command line :
% CXXFLAGS=-pipe ./configure --with-stlport=<STLPort_headers_path>
To get the complete list of arguments of the "configure" script use the
following command :
% ./configure --help
Installation
============
1. Windows installation
-----------------------
Not done yet.
2. GNU/Linux installation
--------------------------
% make install
</PRE>
|
