3 |
|
|
4 |
|
This file describes how to build and install Radiance using the SCons |
5 |
|
based build system (an alternative to the traditional makeall script |
6 |
< |
expleined in the README file). |
6 |
> |
explained in the README file). |
7 |
|
|
8 |
|
|
9 |
|
Requirements |
10 |
|
------------ |
11 |
|
|
12 |
|
Please make sure that you have dowloaded and unpacked BOTH the Radiance |
13 |
< |
source package AND the archive with the auxiliary files. Crucial parts |
14 |
< |
of the system will be missing if you only have one of them. |
13 |
> |
source package AND the archive with the auxiliary support files. |
14 |
> |
Crucial parts of the system will be missing if you only have one of |
15 |
> |
them, and SCons will be unable to build the software. |
16 |
|
|
17 |
|
SCons is a platform-independent software configuration and build system |
18 |
|
written in Python. If SCons and Python are not already installed on your |
21 |
|
Python: http://www.python.org/ |
22 |
|
SCons: http://www.scons.org/ |
23 |
|
|
24 |
< |
For many systems, precompiled packages are availabls, such as Installer |
24 |
> |
For many systems, precompiled packages are available, such as Installer |
25 |
|
files for Windows. Most Linux distributions already come with Python |
26 |
|
installed and ready to use. |
27 |
|
|
28 |
< |
SCons *may* use a libtiff already installed on your system. However, if |
29 |
< |
it doesn't find one, it will build its own from sources included with |
30 |
< |
Radiance. |
28 |
> |
SCons *may* use a libtiff already installed on your system. On posix |
29 |
> |
systems it usually does. Otherwise the executables requiring it are |
30 |
> |
not built. |
31 |
|
|
32 |
|
|
33 |
|
Building |
55 |
|
specific combination of operating system and build tools (eg. compiler). |
56 |
|
On unix based systems, the compiler usually doesn't make much of a |
57 |
|
difference, but on Windows, there are seperate build environments for |
58 |
< |
toolkits like Cygwin or MingW. |
58 |
> |
toolkits like MingW. |
59 |
|
|
60 |
|
The file "ray/platform/README" explains the settings that can be |
61 |
|
configured in those files, and how to create a new one, if you use a |
126 |
|
------------ |
127 |
|
|
128 |
|
The software will be installed into the directories given either in the |
129 |
< |
configuration file through command options, by invoking |
129 |
> |
configuration file or through command options, by invoking |
130 |
|
|
131 |
|
$> scons install |
132 |
|
|
148 |
|
To save disk space on your system, or in preparation of a fresh build |
149 |
|
with different settings, you can clean up the source tree by invoking |
150 |
|
|
151 |
< |
%> scons -c |
151 |
> |
$> scons -c |
152 |
|
|
153 |
|
This will delete all the generated object files, libraries, and |
154 |
|
executables in and below the "ray/src/" subdirectory. |