Difference between revisions of "VisIt"
| Line 19: | Line 19: | ||
If you want to use an existing installation of the 3rd party software | If you want to use an existing installation of the 3rd party software | ||
(note that that in some cases VisIt requires older versions) you can | (note that that in some cases VisIt requires older versions) you can | ||
| − | force this with the following [[VisIt:compile_hack hack]] (uses Python as an example): | + | force this with the following [[VisIt:compile_hack | hack]] (uses Python as an example): |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 15:22, 31 October 2008
Installing VisIt 1.10.0
These are notes from Rupert Gladstone. I would need to re-build visit to ensure that these notes are correct.
Download the build VisIt script.
Download the VisIt sources from the downloads page.
Under Setup in the build VisIt script is a list of required 3rd party software. Download all the 'must have' tarballs and HDF5, NetCDF, szip. These can be downloaded from the bottom of the VisIt downloads page.
I also had to download Imaging-1.1.6.tar.gz from here, prompted by a message in the build log.
If you want to use an existing installation of the 3rd party software
(note that that in some cases VisIt requires older versions) you can
force this with the following hack (uses Python as an example):
Run the build VisIt script.
Note that this should give a valid install of VisIt, but VisIt will still not functiona properly when used remotely via ssh/exceed. This is because exceed does not support openGL. See also this Linux forum comment and the exceed website for more info. It would appear that exceed3d could be purchased to get round this problem.