/[escript]/branches/doubleplusgood/doc/install/srclinux.tex
ViewVC logotype

Diff of /branches/doubleplusgood/doc/install/srclinux.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 2455 by jfenwick, Wed Jun 3 03:29:07 2009 UTC revision 2923 by jfenwick, Thu Feb 4 04:05:36 2010 UTC
# Line 1  Line 1 
   
1  %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2  %  %
3  % Copyright (c) 2003-2008 by University of Queensland  % Copyright (c) 2003-2010 by University of Queensland
4  % Earth Systems Science Computational Center (ESSCC)  % Earth Systems Science Computational Center (ESSCC)
5  % http://www.uq.edu.au/esscc  % http://www.uq.edu.au/esscc
6  %  %
# Line 13  Line 12 
12    
13  \section{Installing from source for \linux}  \section{Installing from source for \linux}
14  \label{sec:srclinux}  \label{sec:srclinux}
15    
16    \subsection{Preliminaries}
17    
18  The following instructions assume you are running the \filename{bash} shell.  The following instructions assume you are running the \filename{bash} shell.
19  Comments are indicated with \# characters.  Comments are indicated with \# characters.
20    
21  Make sure you have the following installed:  Make sure you have the following installed:
22  \begin{itemize}  \begin{itemize}
23   \item \filename{g++} and associated tools.   \item \filename{g++} and associated tools.
24  \item \filename{make}   \item \filename{make}
25  \item \filename{libXext.so}\footnote{In Debian this is in the libXext-dev package.}   % I suspect that these are only needed by VTK and if we aren't using it anymore they could be removed
26  \item \filename{libxt.so}\footnote{In Debian this is in the libxt-dev package.}  %  \item \filename{libXext.so}\footnote{In Debian this is in the libXext-dev package.}
27    %  \item \filename{libxt.so}\footnote{In Debian this is in the libxt-dev package.}
28    \end{itemize}
29    
30    To compile matplotlib you will also need the following\footnote{For Debian and Ubuntu users, installing \filename{libfreetype6-dev} and \filename{libpng-dev} will be sufficient.} (if your distribution separates development files,
31    make sure to get the development packages):
32    \begin{itemize}
33     \item \filename{freetype2}
34    \item \filename{zlib}
35    \item \filename{libpng}
36  \end{itemize}  \end{itemize}
37    
38    
39    
40  You will also need a copy of the \esfinley source code.  You will also need a copy of the \esfinley source code.
41  If you retrieved the source using subversion, don't forget that one can use the export command instead of checkout to get a smaller copy.  If you retrieved the source using subversion, don't forget that one can use the export command instead of checkout to get a smaller copy.
42  For additional visualisation functionality see Section~\ref{sec:linaddfunc}.  For additional visualization functionality see \Sec{sec:addfunc}.
43    
44  These instructions will produce the following structure:  These instructions will produce the following directory structure:
45  \begin{itemize}  \begin{itemize}
46  \item \filename{stand}: \begin{itemize}   \item[] \filename{stand} \begin{itemize}
47   \item \filename{escript.d}    \item[] \filename{escript.d}
48  \item \filename{packages}    \item[] \filename{pkg}
49  \item \filename{package_src}    \item[] \filename{pkg_src}
50  \item \filename{build}    \item[] \filename{build}
51  \item \filename{doc}    \item[] \filename{doc}
52    \end{itemize}   \end{itemize}
53  \end{itemize}  \end{itemize}
54    
55  The build directory can be removed when you are finished.  Before you start copy the \esfinley source into the \filename{escript.d} directory.
56    The following instructions refer to software versions in the \filename{escript-support-3-src} bundle.
57    If you download your own versions of those packages substitute their version numbers and names as appropriate.
58    There are a number of uses of the \filename{make} command in the following instructions.
59    If your computer has multiple cores/processors you can speed up the compilation process by adding -j 2 after the make command.
60    For example to use all processors on a computer with 4 cores:
61    \begin{shellCode}
62     make
63    \end{shellCode}
64    becomes
65    \begin{shellCode}
66     make -j 4
67    \end{shellCode}
68    
69  \begin{shellCode}  \begin{shellCode}
70  mkdir stand  mkdir stand
71  cd stand  cd stand
72  export PKG_ROOT=`pwd`/packages  mkdir build doc pkg pkg_src
73    export PKG_ROOT=$(pwd)/pkg
74    \end{shellCode}
75    
76    \subsection{Building the dependencies}
77    
78    Copy the compressed sources for the packages into \filename{stand/pkg_src}.
79    If you are using the support bundles, decompress them in the stand directory:
80    \begin{shellCode}
81    tar -xjf escript-support-3-src.tar.bz2
82  \end{shellCode}  \end{shellCode}
83    
84  Copy compressed source bundles into \filename{stand/package_src}.  Copy documentation files into \filename{doc} then unpack the archives:
 Copy documentation files into \filename{doc}.  
85    
86  \begin{shellCode}  \begin{shellCode}
 mkdir packages  
 mkdir build  
87  cd build  cd build
88  tar -jxf ../package_src/Python-2.6.1.tar.bz2  tar -jxf ../pkg_src/Python-2.6.2.tar.bz2
89  tar -jxf ../package_src/boost_1_37_0.tar.bz2  tar -jxf ../pkg_src/boost_1_39_0.tar.bz2
90  tar -jxf ../package_src/MesaLib-7.2.tar.bz2  tar -zxf ../pkg_src/scons-1.2.0.tar.gz
91  tar -zxf ../package_src/netcdf-4.0.tar.gz  tar -zxf ../pkg_src/numpy-1.3.0.tar.gz
92  tar -zxf ../package_src/vtk-5.2.1.tar.gz  tar -zxf ../pkg_src/netcdf-4.0.tar.gz
93  tar -zxf ../package_src/vtkdata-5.2.1.tar.gz  tar -zxf ../pkg_src/matplotlib-0.98.5.3.tar.gz
 tar -zxf ../package_src/numarray-1.5.2.tar.gz  
 tar -zxf ../package_src/cmake-2.6.3.tar.gz  
 tar -zxf ../package_src/scons-1.2.0.tar.gz  
94  \end{shellCode}  \end{shellCode}
95    
96  Build python.  \begin{itemize}
97    
98    \item Build Python:
99  \begin{shellCode}  \begin{shellCode}
100  cd Python*  cd Python*
101  ./configure --prefix=$PKG_ROOT/python-2.6.1 --enable-shared 2>&1 \  ./configure --prefix=$PKG_ROOT/python-2.6.2 --enable-shared 2>&1 \
102    | tee tt.configure.out    | tee tt.configure.out
103    make
104  make install 2>&1 | tee tt.make.out  make install 2>&1 | tee tt.make.out
105    
106  cd ..  cd ..
# Line 78  export PATH=$PKG_ROOT/python/bin:$PATH Line 109  export PATH=$PKG_ROOT/python/bin:$PATH
109  export PYTHONHOME=$PKG_ROOT/python  export PYTHONHOME=$PKG_ROOT/python
110  export LD_LIBRARY_PATH=$PKG_ROOT/python/lib:$LD_LIBRARY_PATH  export LD_LIBRARY_PATH=$PKG_ROOT/python/lib:$LD_LIBRARY_PATH
111    
112  pushd ../packages  pushd ../pkg
113  ln -s python-2.6.1/ python  ln -s python-2.6.2/ python
114  popd  popd
   
115  \end{shellCode}  \end{shellCode}
116    
117  Run python to make sure it works.  Run the new python executable to make sure it works.
 Now build numarray.  
118    
119    \item Now build NumPy:
120  \begin{shellCode}  \begin{shellCode}
121  cd numarray-1.5.2  cd numpy-1.3.0
122    python setup.py build
123  python setup.py install \  python setup.py install --prefix $PKG_ROOT/numpy-1.3.0
  --gencode --install-lib=$PKG_ROOT/numarray-1.5.2/lib \  
  --install-headers=$PKG_ROOT=$PKG_ROOT/numarray-1.5.2/include/numarray \  
    2>&1 | tee tt.install.out  
   
   
 export PYTHONPATH=$PKG_ROOT/numarray/lib:$PYTHONPATH  
124  cd ..  cd ..
125  pushd ../packages  pushd ../pkg
126  ln -s numarray-1.5.2 numarray  ln -s numpy-1.3.0 numpy
127  popd  popd
128    export PYTHONPATH=$PKG_ROOT/numpy/lib/python2.6/site-packages:$PYTHONPATH
129  \end{shellCode}  \end{shellCode}
130    
131  Now we build scons.  % \begin{shellCode}
132    % cd numarray-1.5.2
133    %
134    % python setup.py install \
135    %  --gencode --install-lib=$PKG_ROOT/numarray-1.5.2/lib \
136    %  --install-headers=$PKG_ROOT=$PKG_ROOT/numarray-1.5.2/include/numarray \
137    %    2>&1 | tee tt.install.out
138    %
139    %
140    % export PYTHONPATH=$PKG_ROOT/numarray/lib:$PYTHONPATH
141    % cd ..
142    % pushd ../pkg
143    % ln -s numarray-1.5.2 numarray
144    % popd
145    % \end{shellCode}
146    
147    \item Next build scons:
148  \begin{shellCode}  \begin{shellCode}
149  cd scons-1.2.0  cd scons-1.2.0
150  python setup.py install --prefix=$PKG_ROOT/scons-1.2.0  python setup.py install --prefix=$PKG_ROOT/scons-1.2.0
151    
152  export PATH=$PKG_ROOT/scons/bin:$PATH  export PATH=$PKG_ROOT/scons/bin:$PATH
153  cd ..  cd ..
154  pushd ../packages  pushd ../pkg
155  ln -s scons-1.2.0 scons  ln -s scons-1.2.0 scons
156  popd  popd
157  \end{shellCode}  \end{shellCode}
158    
159  ...Boost libraries ...  \item The Boost libraries...:
160  \begin{shellCode}  \begin{shellCode}
161  cd boost_1_37_0  pushd ../pkg
162    mkdir boost_1_39_0
163  ./configure --prefix=$PKG_ROOT/boost_1_37_0 --with-python-root=$PKG_ROOT/python \  ln -s boost_1_39_0 boost
164    --with-python-version=2.6 --with-libraries=python  popd
165    cd boost_1_39_0
166  make  ./bootstrap.sh --with-libraries=python --prefix=$PKG_ROOT/boost
167  make install  ./bjam
168  ln -s $PKG_ROOT/boost_1_37_0 $PKG_ROOT/boost  ./bjam install --prefix=$PKG_ROOT/boost --libdir=$PKG_ROOT/boost/lib
169  export LD_LIBRARY_PATH=$PKG_ROOT/boost/lib:$LD_LIBRARY_PATH  export LD_LIBRARY_PATH=$PKG_ROOT/boost/lib:$LD_LIBRARY_PATH
170  cd ..  cd ..
171  pushd ../packages  pushd ../pkg/boost/lib/
172  ln -s boost_1_37_0 boost  ln *.so.* libboost_python.so
173  popd  popd
174  \end{shellCode}  \end{shellCode}
175    
176  ... and netcdf.  \item ...and NetCDF:
177  \begin{shellCode}  \begin{shellCode}
178  cd netcdf-4.0  cd netcdf-4.0
179  CFLAGS="-O2 fPIC -Df2cFortran" CXXFLAGS="-O2 fPIC -Df2cFortran" \  CFLAGS="-O2 -fPIC -Df2cFortran" CXXFLAGS="-O2 -fPIC -Df2cFortran" \
180  FFLAGS="-O2 fPIC -Df2cFortran" FCFLAGS="-O2 fPIC -Df2cFortran" \  FFLAGS="-O2 -fPIC -Df2cFortran" FCFLAGS="-O2 -fPIC -Df2cFortran" \
181  ./configure --prefix=$PKG_ROOT/netcdf-4.0  ./configure --prefix=$PKG_ROOT/netcdf-4.0
182    
183  make -j2  make
184  make install  make install
185    
186  export LD_LIBRARY_PATH=$PKG_ROOT/netcdf/lib:$LD_LIBRARY_PATH  export LD_LIBRARY_PATH=$PKG_ROOT/netcdf/lib:$LD_LIBRARY_PATH
187  cd ..  cd ..
188  pushd ../packages  pushd ../pkg
189  ln -s netcdf-4.0 netcdf  ln -s netcdf-4.0 netcdf
190  popd  popd
191  \end{shellCode}  \end{shellCode}
192    
193  CMake and Mesa are required for VTK.  \item Finally matplotlib:
194  \begin{shellCode}  \begin{shellCode}
195  cd cmake-2.6.3  cd matplotlib-0.98.5.3
196  ./configure --prefix=$PKG_ROOT/cmake-2.6.3 2>&1 | tee tt.configure  python setup.py build
197  make -j 4  python setup.py install --prefix=$PKG_ROOT/matplotlib-0.98.5.3
 make install  
   
 export PATH=$PKG_ROOT/cmake/bin:$PATH  
198  cd ..  cd ..
199  pushd ../packages  pushd ../pkg
200  ln -s cmake-2.6.3 cmake  ln -s matplotlib-0.98.5.3 matplotlib
201  popd  popd
 \end{shellCode}  
   
 These instructions do not compile MesaDemos or GLUT.  
 If you need to check if Mesa compiled correctly, then the demos are a good test.  
 \begin{shellCode}  
 cd Mesa-7.2  
 ./configure --prefix=$PKG_ROOT/mesa-7.2 --enable-gl-osmesa --with-driver=xlib  
   
 make -j 4  
 make install  
   
 export LD_LIBRARY_PATH=$PKG_ROOT/mesa:$LD_LIBRARY_PATH  
202  cd ..  cd ..
 pushd ../packages  
 ln -s mesa-7.2 mesa  
 popd  
203  \end{shellCode}  \end{shellCode}
204    
205  \begin{shellCode}  \end{itemize}
 cd VTK  
 cmake .  
   
 #Edit the CMakeCache and make the following changes:  
 #(Please replace .... with an absolute path to the stand directory)  
   
 #-----------------  
   
 BUILD_EXAMPLES should be OFF  
 BUILD_SHARED_LIBS should be ON  
   
 CMAKE_INSTALL_PREFIX    ..../stand/packages/vtk-5.2.1  
 CMAKE_VERBOSE_MAKEFILE  TRUE  
   
 #check PYTHON_EXECUTABLE is correct.  
 #but it seems to be when I went through these steps  
   
 VTK_OPENGL_HAS_OSMESA   TRUE  
 VTK_USE_64BIT_IDS   ON  
 # That last one is marked as "May cause some bugs" in the original instructions  
   
 VTK_WRAP_PYTHON ON  
 VTK_USE_MANGLED_MESA    OFF  
   
 #--------------------  
   
 cmake .  
 #It won't work but it will put some variables in that you need.  
   
 #Edit CMakeCache again and make the following changes  
   
 #----------------  
   
 VTK_USE_TK  OFF  
   
 OSMESA_INCLUDE_DIR  ..../stand/packages/mesa/include  
   
 OSMESA_LIBRARY  ..../stand/packages/mesa/lib/libOSMesa.so  
   
 PYTHON_INCLUDE_PATH ..../stand/packages/python/include/python2.6  
   
 PYTHON_LIBRARY  ..../stand/packages/python/lib/libpython2.6.so  
   
 OPENGL_INCLUDE_DIR  ..../stand/packages/mesa/include  
   
 OPENGL_gl_LIBRARY   ..../stand/packages/mesa/lib/libGL.so  
   
 #----------------  
   
 cmake .  
   
 chmod +w Utilities/vtktiff/tif_fax3sm.c  
   
 make  
 make install  
   
   
 cd ../../packages  
 ln -s vtk-5.2.1 vtk  
 cd ..  
 \end{shellCode}  
206    
207  Now copy the \esfinley source into an \filename{escript.d} directory in \filename{stand}.  % \subsection{VTK support}
208    % VTK is only required for pyvisi. To build it you need CMake and Mesa.
209    % The packages can be downloaded independently or in the \filename{escript-support-visi-3-src}.
210    % If you will not be using pyvisi, then skip to \Sec{sec:compileescriptlinux}
211    %
212    % Copy the compressed sources for the packages into \filename{stand/pkg_src}.
213    % If you are using the support bundles, decompress them in the stand directory.
214    % \begin{shellCode}
215    % tar -xjf escript-support-visi-3-src.tar.bz2
216    % \end{shellCode}
217    %
218    % \begin{shellCode}
219    % cd build
220    % tar -jxf ../pkg_src/MesaLib-7.2.tar.bz2
221    % tar -zxf ../pkg_src/vtk-5.2.1.tar.gz
222    % tar -zxf ../pkg_src/vtkdata-5.2.1.tar.gz
223    % tar -zxf ../pkg_src/cmake-2.6.3.tar.gz
224    % \end{shellCode}
225    %
226    % \begin{itemize}
227    %
228    % \item Build CMake:
229    % \begin{shellCode}
230    % cd cmake-2.6.3
231    % ./configure --prefix=$PKG_ROOT/cmake-2.6.3 2>&1 | tee tt.configure
232    % make
233    % make install
234    %
235    % export PATH=$PKG_ROOT/cmake/bin:$PATH
236    % cd ..
237    % pushd ../pkg
238    % ln -s cmake-2.6.3 cmake
239    % popd
240    % \end{shellCode}
241    %
242    % \item Build Mesa:
243    % \begin{shellCode}
244    % cd Mesa-7.2
245    % ./configure --prefix=$PKG_ROOT/mesa-7.2 --enable-gl-osmesa --with-driver=xlib
246    %
247    % make
248    % make install
249    %
250    % export LD_LIBRARY_PATH=$PKG_ROOT/mesa/lib:$LD_LIBRARY_PATH
251    % cd ..
252    % pushd ../pkg
253    % ln -s mesa-7.2 mesa
254    % popd
255    % \end{shellCode}
256    % These instructions do not compile MesaDemos or GLUT.
257    % If you need to check if Mesa compiled correctly, then the demos are a good test.
258    %
259    % \item Finally, build VTK:
260    % \begin{shellCode}
261    % cd VTK
262    % cmake .
263    % \end{shellCode}
264    %
265    % Now edit the \filename{CMakeCache.txt} file and make the following changes.
266    % Where .... appears please replace it with the absolute path to the pkg directory.
267    % For example, replace \filename{CMAKE_INSTALL_PREFIX:PATH=..../vtk-5.2.1} with
268    % \filename{CMAKE_INSTALL_PREFIX:PATH=/home/bob/stand/pkg/vtk-5.2.1}
269    % (Search for the text before the =).
270    % \begin{shellCode}
271    % BUILD_EXAMPLES:BOOL=OFF
272    % BUILD_SHARED_LIBS:BOOL=ON
273    % CMAKE_INSTALL_PREFIX:PATH=..../vtk-5.2.1
274    % CMAKE_VERBOSE_MAKEFILE:BOOL=TRUE
275    % VTK_OPENGL_HAS_OSMESA:BOOL=TRUE
276    % VTK_USE_64BIT_IDS:BOOL=ON
277    % VTK_WRAP_PYTHON:BOOL=ON
278    % VTK_USE_MANGLED_MESA:BOOL=OFF
279    % \end{shellCode}
280    %
281    % Now rerun cmake (it won't work but it adds some variables you need).
282    %
283    % \begin{shellCode}
284    % cmake .
285    % \end{shellCode}
286    %
287    % Edit \filename{CMakeCache.txt} and change the following variables:
288    %
289    % \begin{shellCode}
290    % VTK_USE_OFFSCREEN:BOOL=ON
291    % VTK_USE_TK:BOOL=OFF
292    % OSMESA_INCLUDE_DIR:PATH=..../mesa/include
293    % OSMESA_LIBRARY:FILEPATH=..../mesa/lib/libOSMesa.so
294    % PYTHON_INCLUDE_PATH:PATH=..../python/include/python2.6
295    % PYTHON_LIBRARY:FILEPATH=..../python/lib/libpython2.6.so
296    % OPENGL_INCLUDE_DIR:PATH=..../mesa/include
297    % OPENGL_gl_LIBRARY:FILEPATH=..../mesa/lib/libGL.so
298    % \end{shellCode}
299    %
300    % The following steps will take a while so grab a coffee while it compiles.
301    % \begin{shellCode}
302    % cmake .
303    % make
304    % chmod +w Utilities/vtktiff/tif_fax3sm.c
305    % make install
306    %
307    % cd ../../pkg
308    % ln -s vtk-5.2.1 vtk
309    % cd ..
310    % \end{shellCode}
311    %
312    % \end{itemize}
313    
314  \subsection{Compiling escript}\label{sec:compileescriptlinux}  \subsection{Compiling escript}\label{sec:compileescriptlinux}
315    
316  Change to the directory containing your escript source (\filename{escript.d}), then:  Change to the directory containing your escript source (\filename{stand/escript.d}), then:
317    
318  \begin{shellCode}  \begin{shellCode}
319  cd scons  cd escript.d/scons
320  cp linux_options_example.py YourMachineName_options.py  cp linux_standalone_options_example.py YourMachineName_options.py
321    
322  #edit the options file and make the following changes:  echo $PKG_ROOT
323  #-----------------------------------------------------------------  \end{shellCode}
324  declare a PKG_ROOT variable at the top of the file eg:  Where \texttt{YourMachineName} is the name of your computer as returned by the hostname command.
325  PKG_ROOT='/home/jfenwick/stand/packages'  If the name contains non-alphanumeric characters, then you will need to replace them with underscores.
326    For example the options file for \texttt{bob-desktop} would be named \filename{bob_desktop_options.py}.
 python_path     = PKG_ROOT+'python/include/python2.6'  
 python_lib_path     = PKG_ROOT+'python/lib'  
 python_libs     = 'python2.6'  
   
 boost_path      = PKG_ROOT+'boost/include/boost-1_37'  
 boost_lib_path      = PKG_ROOT+'boost/lib'  
 boost_libs      = ['boost_python-gcc43-mt']  
 # You could simlink the boost python library to give a shorter  
 # name but it's not worth it  
   
 usevtk      = 'yes'  
 #-------------------------------------------------------------------  
327    
328  ln -s $PKG_ROOT/vtk-5.2.1 $PKG_ROOT/vtk  Edit the options file and put the value of PKG_ROOT between the quotes in the PKG_ROOT= line.
329    For example:
330    \begin{shellCode}
331    PKG_ROOT="/home/bob/stand/pkg"
332    \end{shellCode}
333    
334  Modify bin/escript  \begin{shellCode}
335    cd ../bin
336    \end{shellCode}
337    
338    Modify the STANDALONE line of \filename{run-escript} to read:
339    
340  STANDALONE=1  STANDALONE=1
341    
342  #Check to make sure the paths in the if [ $STANDALONE == 1 ]  Start a new terminal and go to the \filename{stand} directory.
 #block are correct  
343    
344  #-----------------------------------------------------------------  \begin{shellCode}
345    export PATH=$(pwd)/pkg/scons/bin:$PATH
 #start a new terminal  
 cd stand  
 export PATH=`pwd`/packages/scons/bin:$PATH  
346  cd escript.d  cd escript.d
347  eval `bin/escript -e`  eval $(bin/run-escript -e)
348  scons  scons
349  \end{shellCode}  \end{shellCode}
350    
351  If you wish to test your build, then you can do the following.  If you wish to test your build, then you can do the following.
352  Note this may take a while if you have a slow processor and/or less than 1Gb of RAM.  Note this may take a while if you have a slow processor and/or less than 1GB of RAM.
353  \begin{shellCode}  \begin{shellCode}
354  scons all_tests  scons all_tests
355  \end{shellCode}  \end{shellCode}
# Line 298  scons all_tests Line 357  scons all_tests
357  \subsection{Cleaning up}  \subsection{Cleaning up}
358  Once you are satisfied, the \filename{escript.d/build} and \filename{\$PKG_ROOT/build} directories can be removed.  Once you are satisfied, the \filename{escript.d/build} and \filename{\$PKG_ROOT/build} directories can be removed.
359    
360  If you \emph{really} want to save space and do not wish to be able to edit or recompile escript, you can remove the following:  If you \emph{really} want to save space and do not wish to be able to edit or recompile \esfinley, you can remove the following:
361  \begin{itemize}  \begin{itemize}
362   \item From the \filename{escript.d} directory:\begin{itemize}   \item From the \filename{escript.d} directory:\begin{itemize}
363  \item Everything except: \filename{bin}, \filename{include}, \filename{lib}, \filename{esys},  \item Everything except: \filename{bin}, \filename{include}, \filename{lib}, \filename{esys},
364  \filename{README_LICENSE}.  \filename{README_LICENSE}.
365  \item Hidden files, which can be removed using  \item Hidden files, which can be removed using
366  \begin{shellCode}  \begin{shellCode}
367  find . -name .?* | xargs rm -rf  find . -name '.?*' | xargs rm -rf
368  \end{shellCode}  \end{shellCode}
369  in the \filename{escript.d} directory.  in the \filename{escript.d} directory.
370  \end{itemize}  \end{itemize}
371  \item from the \filename{packages} directory:  \item from the \filename{pkg} directory:
372  \begin{itemize}  \begin{itemize}
373  \item  \filename{scons}, \filename{scons-1.2.0}, \filename{cmake-2.6.3} and \filename{cmake}  \item  \filename{scons}, \filename{scons-1.2.0}, \filename{cmake-2.6.3} and \filename{cmake}
374  \end{itemize}  \end{itemize}
# Line 319  in the \filename{escript.d} directory. Line 378  in the \filename{escript.d} directory.
378  Please note that removing all these files may make it more difficult for us to diagnose problems.  Please note that removing all these files may make it more difficult for us to diagnose problems.
379    
380    
   
   
 \section{Additional Functionality}\label{sec:linaddfunc}  
 To perform visualisations you will need some additional tools.  
 Since these do not need to be linked with any of the packages above, you can install versions available for your  
 system, or build them from source.  
 \begin{itemize}  
 \item \filename{ppmtompeg} and \filename{jpegtopnm} from the \filename{netpbm} suite. - To build from source  
 you would also need \filename{libjpeg} and its headers as well as \filename{libpng}\footnote{libpng requires zlib to build} and its headers.  
 \item A tool to visualise VTK files. For example Mayavi or Visit.  
 \end{itemize}  

Legend:
Removed from v.2455  
changed lines
  Added in v.2923

  ViewVC Help
Powered by ViewVC 1.1.26