- The new cmake seems to be even smarter. If we try to use env variables in
the .cmake files (eg, with And's sed fixup), they are rewritten in a
subsequent re-make and take much longer). Adjusting the compiler values
themselves causes a full remake. On the positive side, disabling the rpath
seems to mean we may not need any of this.
In summary - yuck!
- usage, explicit -fast option for rebuilding new -mpi, -python, -mesa
options for specifying alternative modules to include without editing
the file
- the build options can also be grabbed from the script name itself.
eg, the soft-link buildParaView3.3-cvs-python specifies that the python
module should be included
- misc. cleanup in tools/buildParaViewFunctions: give the user some
feedback about the python version, set all variables at the bottom
of the file rather between initialise and build.
- be more careful when changing the hard-links to avoid the find
'-execdir' option (fails when the user has '.' in the path), and
do separate find/loop/grep/sed on the files to avoid touching too many
files and ruining a later rebuild stage.
Notes:
- the cmake uses -DCMAKE_INSTALL_PREFIX=$PARAVIEW_APP_DIR, but this
variable isn't defined anywhere.
replace the $OPENMPI_ARCH_PATH with $ENV{OPENMPI_ARCH_PATH} in the *.cmake files.
Note this change is specific to OpenMPI and will need genaralising, Andy?
