The following is a full description of all Open Inventor by Mercury (Open Inventor, ScaleViz, MeshViz, VolumeViz...) files.
| data/ | Directory containing Open Inventor data files, including sample geometry files, materials, patterns, etc. | ||
| doc/ | Directory containing documentation files | ||
|
include/ |
Directory containing the Open Inventor include files
Includes for ReservoirViz module |
||
|
Inv720.lib
MeshVizExtractor720.lib MeshVizDataMapping720.lib MeshVizDataMapping720D.lib
MeshVizImpl720.lib ReservoirViz720.lib |
Directory containing the Open Inventor libraries Open Inventor Release library
MeshViz Interface Extractor Release library with Win32 references
MeshViz Interface Data Mapping Release library with Win32 references
MeshViz Interface Implementation Release library with Win32 references ReservoirViz Release library with no Win32 references |
||
| license/ | Directory containing license admin program. | ||
| License.txt | User license agreement | ||
| Program/ |
|
||
| proprietary | Open Inventor proprietary statement | ||
| ReadMe/ | Directories containing ReadMe files in clear text. | ||
| ReadMe1st.txt | File to read first. | ||
| src/ DialogViz/ FXViz/ HardCopy/ Inventor/ MeshViz/ MeshIViz/ ReservoirViz/ ScaleViz/ SolidViz/ TerrainViz/ VolumeViz/ Inventor/contrib |
Directory
containing examples and demos Directory containing DialogViz examples Directory containing FXViz examples Directory containing HardCopy examples Directory containing Open Inventor examples Directory containing MeshViz examples Directory containing MeshViz Interface examples Directory containing ReservoirViz examples Directory containing ScaleViz examples Directory containing SolidViz examples Directory containing TerrainViz examples Directory containing VolumeViz examples Directory containing miscellaneous source and/or executables. Some of these programs were written by Mercury Computer Systems, but are not supported products. |
NOTE:
For run-time licenses, the only files necessary are the program executable,
the password file, and any required data files. If the application is linked
dynamically (always the case on Windows), (e.g., with .so or .sl
libraries on UNIX and .dll on Windows), shared libraries
on UNIX or DLLs on Windows must be provided. No other Open
Inventor files need (or should) be present.
For a complete explanation of Open Inventor run-time distributions, see the
Redistribution topic.
Open Inventor provides standard libraries and shared libraries for all UNIX
platforms.
Shared libraries provide the following advantages:
- dramatically reduced executable size
- reduced link time
- ability to use updated shared libraries without relinking at the expense of a slight increase in program startup time.
On SGI, SUN, Digital, and Linux machines, shared libraries are suffixed .so,
on HP: .sl
on IBM: _s.a
On SGI, SUN, and HP, no special action is required to take advantage of shared libraries. Makefiles will automatically use Open Inventor shared libraries by default assuming that your makefile uses the usual "-L$OIVHOME/lib -lInventorXt -lInventor -limage ... " format. On SGI, SUN, and HP, don't try to link system libraries statically. This can produce bad executables. To disable the use of shared libraries:
- On SUN: Add the -B static -B dynamic flags at link-time:
Example:
-B static -L$OIVHOME/lib -lInventorXt -lInventor -limage -B dynamic.
ldd can be used to list the shared libraries linked with a program.
LD_LIBRARY_PATH must be set at run-time.
- On SGI: Add the -B static -B dynamic at link-time:
Example:
-B static -L$OIVHOME/lib -lInventorXt -lInventor -limage -B dynamic
NOTE: Don't write -Bstatic instead of -B static. This is a different option!
elfdump -Dl can be used to list the shared libraries linked with a program.
LD_LIBRARY_PATH must be set at run-time.
- On HP: Add the -Wl,-a,archive -Wl,-a,default flags at link-time:
Example:
-Wl,-a,archive -L$OIVHOME/lib -lInventorXt -lInventor -limage
-Wl,-a,default.
chatr can be used to list the shared libraries linked with a program.
- On IBM: The library base name is different for archive and shared libraries.
Example:
- Dynamic linking:
L$OIVHOME/lib -lInventorXt_s -lInventor_s -limage_s
- Static linking:
L$OIVHOME/lib -lInventorXt -lInventor -limage