If you would like to be notified about new updates, please send a request to email@example.com
IFrIT is distributed under the terms of GNU Public License (GPL)
. If you use the GUI shell with IFrIT, the specific version of the GPL license is inherited from the GPL version of Qt; if you do not use GUI, then version 2 is in effect. By downloading IFrIT you are agreeing to abide by the terms of GPL.
Latest Version (IFrIT 4 - currently in Beta):
The VTK and GADGET extensions also serve as a tutorial
on how to write IFrIT extensions if you want to teach IFrIT to read
your favorite data format. I release both these extensions as
beta-versions, since I do not have access to many data files in these
formats. The released extensions do read all files supplied with VTK
and GADGET distributions.
- ART Extension for reading ART data files and doing the full set of AMR visualizations.
- Multi-View Extension
for using multiple monitor setups (Wall- and Cave-like, planetarium
domes, dual monitors, etc). Since these set-ups are not that common,
this extension is not compiled in by default, you will need to run
CMake interactively (using cmake -i or ccmake) to
include it. Many set-ups are still missing, but they are very easy to
add, so if you need something, drop me a line.
A Windows installer can be provided on request.
Previous Version (IFrIT 3)
Install Other Packages
Before you can compile IFrIT, you need to install other packages that IFrIT uses:
- Required for compiling the source: Kitware VTK
(Visualization Toolkit for 3D visualizations, public domain). IFrIT has
been ported to VTK versions 5.6 and above. Support to earlier VTK versions is now discontinued. Do not download later
versions (so-called Nightly releases), they might not compile or
function properly. I recommend using VTK 6, as this is now the latest version and IFrIT is better tested with it.
- Optional: Trolltech Qt
(a multi-platform GUI library, open source). IFrIT has been ported to
Qt versions from 3.0.4 to 5.4.0 (later versions will most likely work too, but I haven't checked them yet). At the moment I recommend using Qt 3,
since Qt 4 and 5 do not add any new capabilities that I use and are somewhat
slower than version 3; it is also less savvy in using the screen space.
The only reason to use Qt 4 or 5 is because they are free on Windows, while Qt
3 is not (I also provide the Windows installer, so Windows users do not
even have to worry about installing Qt or VTK).
(Download Qt 3.3.0 source - Mac users should get a free Mac version of Qt, do not use the X11 version.) If you use KDE on Linux, then you already have Qt installed, but you may need to ask your sysadmin to install a developer package, with include files and moc executable.
Important: Qt is needed for GUI support. Without Qt, only the command-line version of IFrIT will be available.
To compile IFrIT, follow the steps:
- Untar IFrIT source file; it creates a ifrit-NNN directory (where
NNN is the version of IFrIT). If you would like to install extensions,
untar them inside the ifrit-NNN directory.
- Set the environment variables VTK_DIR to point to the VTK root directory. If you use Qt, the environment variable QTDIR
should also be defined (it is defined automatically, if Qt is installed
correctly), and Qt bin directory ($QTDIR/bin) should be in your path.
- Switch to ifrit-NNN/build directory (where NNN is the version of IFrIT).
- Use CMake to configure IFrIT - since you installed VTK, you
should have a working version of CMake too. The simplest way to
configure IFrIT is to run non-interactive CMake:
% cmake .
If you would like to use CMake options to disable some of the
components or need more control over the build process (if, for
example, some of the standard libraries are not in standard places),
you can run CMake interactively:
% cmake -i .
(in the command-line mode) or
% ccmake .
for the GUI mode (ccmake is called cmake-gui.exe
under Windows). In most cases configuring in GUI mode reduces to
pressing "c" a few times, and then pressing "g". If CMake complains
about VTK changing compiler switches, accept the VTK choice. If
completed successfully, CMake will create a Makefile in the current
directory. You will need to use the interactive mode if you would like
to add the Multi-View extension, it is off by default.
- Compile IFrIT by executing
It will take some time to compile. The executable is called "ifrit" and
is located in the main source directory (one level above build).
Move it into your personal bin directory. The executable is
self-containing, it does not need any other files to run (but you can
use external files to modify IFrIT behavior).
- For Windows, I can provide self-extracting installers for 32-bit and 64-bit versions upon request.
- I have only limited access to Mac platforms; it was reported some time ago that an advanced CMake option CMAKE_EXE_LINKER_FLAGS needs to be set to "-framework OpenGL -framework GLUT" on a Mac; that option can also be supplied on the CMake command line as
- -D CMAKE_EXE_LINKER_FLAGS="-framework OpenGL -framework GLUT"
- CMake switch StereoSupport is set by default. It controls whether IFrIT activates the OpenGL support for stereo hardware (many high- and medium-end graphic cards support stereo in hardware nowadays). I got a report that stereo hardware support in IFrIT caused flicker on a Mac. Turning off this option will disable stereo hardware support (but you can still use other stereo options, like dual windows or blue-red stereo).
- Advanced options can be used to solve some of the porting issues:
- Port:NoLongLong will turn off usage of long long int type. If the compiler complains of underfined long long type, enable this option.
Enjoy! Do not forget to glance through the User Guide!