ViewVC Help
View File | Revision Log | Show Annotations | Download File | Root Listing
root/radiance/ray/INSTALL.scons
(Generate patch)

Comparing ray/INSTALL.scons (file contents):
Revision 1.1 by schorsch, Fri Dec 26 17:00:32 2008 UTC vs.
Revision 1.5 by schorsch, Tue Apr 19 21:21:23 2016 UTC

# Line 3 | Line 3 | Building and Installing Radiance with SCons
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
# Line 20 | Line 21 | system, then you need to download and install them fir
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 + On Windows, Radiance gets built with MS Visual Studio if present, the
33 + community editions are sufficient.
34 + VS 2013 is currently the most recent version that does it correctly.
35 + VS 2015 also performs the build, but it uses the new "universal CRT"
36 + from Windows 10, which has a bug that corrupts data in text pipes.
37 + A fix is apparently ready and should be released via autoupdate,
38 + probably around the time of the "anniversary update" in summer 2016.
39 + Older versions of VS may work as well, but haven't been tested with
40 + the current sources.
41  
42 +
43   Building
44   --------
45  
# Line 54 | Line 65 | files for various build environments. In this context,
65   specific combination of operating system and build tools (eg. compiler).
66   On unix based systems, the compiler usually doesn't make much of a
67   difference, but on Windows, there are seperate build environments for
68 < toolkits like Cygwin or MingW.
68 > toolkits like MingW.
69  
70   The file "ray/platform/README" explains the settings that can be
71   configured in those files, and how to create a new one, if you use a
# Line 88 | Line 99 | SKIP=1|0
99          1: Skip display of License terms
100          0: Don't skip (default)
101  
102 + MSVC_VERSION=12.0|14.0
103 +        "12.0" is the default for Visual Studio 2013.
104 +        Once the text pipe bug in the universal CRT is fixed, the default
105 +        will be changed to "14.0" for Visual Studio 2015.
106 +
107   SCons will remember the values given with those options. You don't need
108   to supply them again each time when you run repeated builds and
109   installs, but only when something changes.
# Line 125 | Line 141 | Installation
141   ------------
142  
143   The software will be installed into the directories given either in the
144 < configuration file through command options, by invoking
144 > configuration file or through command options, by invoking
145  
146   $> scons install
147  
# Line 147 | Line 163 | Cleanup
163   To save disk space on your system, or in preparation of a fresh build
164   with different settings, you can clean up the source tree by invoking
165  
166 < %> scons -c
166 > $> scons -c
167  
168   This will delete all the generated object files, libraries, and
169   executables in and below the "ray/src/" subdirectory.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines