C++ application on Windows

The following document gives the list of Open Inventor files that your C++ application must embed on Windows.

Most of the required files are DLL libraries located in the folder %OIVHOME%/arch-Windows-x86_64-msvc15-Release/bin or %OIVHOME%/arch-Windows-x86_64-msvc17-Release/bin. %OIVHOME% specifies the root folder where Open Inventor SDK is installed on your machine. This path is referred to as [...]/bin in the rest of this document.

The required files that are described below must be copied in a targeted runtime folder of your application.

Note

You are not allowed to distribute any Open Inventor SDK files that are only used to compile or debug your C++ application. So do not copy any file from the following list:

• %OIVHOME%/include
• %OIVHOME%/arch-Windows-x86_64-msvcXX-debug
• %OIVHOME%/arch-Windows-x86_64-msvcXX-Release/lib
• %OIVHOME%/arch-Windows-x86_64-msvcXX-Release/bin/*.pdb

Inventor Core

kernel (always required)

The following files are required and correspond to the minimal kernel that must copied into the targeted runtime folder of your application.

Component	Windows file name	default path	comments
Inventor	fei_inventor.dll	[...]/bin
	fei_inventor_image.dll	[...]/bin
	fei_inventor_gl.dll	[...]/bin
	fei_inventor_renderengine.dll	[...]/bin
	fei_glew.dll	[...]/bin
Inventor base	fei_inventor_base.dll	[...]/bin
	fei_zlib.dll	[...]/bin
	fei_freetype.dll	[...]/bin
Image access	fei_imageAccess.dll	[...]/bin
boost	fei_boost_system-mt.dll	[...]/bin
boost	fei_boost_date_time-mt.dll	[...]/bin
boost	fei_boost_thread-mt.dll	[...]/bin
boost	fei_boost_iostreams-mt.dll	[...]/bin
boost	fei_boost_filesystem-mt.dll	[...]/bin
boost	fei_boost_log-mt.dll	[...]/bin
Intel TBB	fei_tbb.dll	[...]/bin
ULM	ULMLicenseCheck.dll	[...]/bin
ULM	ULMLicenseCheck_FNP.dll	[...]/bin
dragger data	draggerDefaults/*	%OIVHOME%/data	dragger files
OIV fonts	fonts/*	%OIVHOME%/data	font files

optional files

Depending on file type or specific feature that can be used by your application, the following files may also be necessary. They are dynamically loaded from the application directory, the current directory, the system directory, the Windows directory, %PATH%, or from a path specified by the %OIV_LD_LIBRARY_PATH% environment variable.

Component	Windows file name	default path	comments
	fei_proj4.dll	[...]/bin	required only by SoGeoProjection: Cartographic projection support
	fei_libjpeg.dll	[...]/bin	required only if JPEG images are used, e.g. with SoTexture2 or SoJPEGImageRW
	fei_inventor_io_cad.dll	[...]/bin	required only by SoCADInputReader to import several types of CAD file
	fei_inventor_io_stl.dll	[...]/bin	required only by SoSTLInputReader to import STL file
	fei_inventor_io_dxf.dll	[...]/bin	required only to import DXF file
	fei_inventor_io_vrml.dll	[...]/bin	required only to import VRML file
	fei_smlib.dll	[...]/bin	required only by SoCSGShape

Note

Your application can ask Open Inventor to load alternate versions of these DLLs. For this, you have to use the following environment variables:

• OIV_LIBPROJ4_NAME: Cartographic projection support
• OIV_LIBJPEG_NAME: JPEG support (import/export)
• OIV_ZLIB_NAME: Compression library
• OIV_FREETYPE_NAME: FreeType font support

If you have chosen to use one or more alternate DLLs, be sure to distribute the alternate DLLs that your application needs.

Viewers

Win viewers

If your application uses some classes in Win, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_inventor_ui.dll	[...]/bin
	fei_scaleViz.dll	[...]/bin
	fei_inventor_ui_win.dll	[...]/bin
	fei_inventor_ui_win_resources	[...]/bin

Qt viewers

If your application uses some classes in Qt, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_inventor_ui.dll	[...]/bin
	fei_scaleViz.dll	[...]/bin
	fei_inventor_ui_Qt.dll	[...]/bin
	Qt5Widgets.dll	[...]/bin
	Qt5Core.dll	[...]/bin
	Qt5Gui.dll	[...]/bin

Qt viewer components

If your application uses some classes in Qt ViewerComponents, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_inventor_ViewerComponents.dll	[...]/bin
	fei_inventor_QtViewerComponents.dll	[...]/bin
	Qt5Widgets.dll	[...]/bin
	Qt5Network.dll	[...]/bin
	Qt5Quick.dll	[...]/bin
	Qt5QmlModels.dll	[...]/bin
	Qt5Qml.dll	[...]/bin
	Qt5QmlWorkerScript.dll	[...]/bin

Win viewer components

If your application uses some classes in Win ViewerComponents, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_inventor_ViewerComponents.dll	[...]/bin
	fei_inventor_WinViewerComponents.dll	[...]/bin

MFC viewer components

If your application uses some classes in MFC Viewer Components, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_inventor_ViewerComponents.dll	[...]/bin
	fei_inventor_MFCViewerComponents.dll	[...]/bin

Base view

The following dlls are necessary if your application use one of the following:

• the class PoSceneView
• the class PoView

Component	Windows file name	default path	comments
	fei_inventor_ui.dll	[...]/bin
	fei_scaleViz.dll	[...]/bin

Extensions

VolumeViz extension

If your application uses some classes in VolumeViz or in LDM, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
VolumeViz	fei_volumeViz.dll	[...]/bin
LDM	fei_ldm.dll	[...]/bin
	fei_inventor_ui.dll	[...]/bin
	fei_scaleViz.dll	[...]/bin
	fei_inventor_computing_algorithms.dll	[...]/bin
	fei_libjpeg.dll	[...]/bin	required only if using jpeg files

RemoteViz, (server side)

If your application uses some classes in RemoteViz, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_remoteViz_services.dll	[...]/bin
	fei_remoteViz_jpeg_codec.dll	[...]/bin
	fei_remoteViz_nvidia_video_codec.dll	[...]/bin
	fei_remoteViz_png_codec.dll	[...]/bin
	fei_remoteViz_FFmpeg_codec.dll	[...]/bin
	fei_FFmpeg_avcodec.dll	[...]/bin
	fei_FFmpeg_avfilter.dll	[...]/bin
	fei_FFmpeg_avformat.dll	[...]/bin
	fei_FFmpeg_avutil.dll	[...]/bin
	fei_FFmpeg_swresample.dll	[...]/bin
	fei_FFmpeg_swscale.dll	[...]/bin

RemoteViz, (client side)

If you want to build a client application without any browser, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_remoteViz_client.dll	[...]/bin

MeshViz

If your application uses some classes in MeshViz, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_meshViz.dll	[...]/bin

MeshViz XLM

If your application uses some classes in MeshVizXLM, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_meshVizXLM_dataMapping.dll	[...]/bin
	fei_meshVizXLM_extractor.dll	[...]/bin

Medical

If your application uses some classes in Medical, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_inventor_medical.dll	[...]/bin

ImageViz

If your application uses some classes in ImageViz, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_imageViz.dll	[...]/bin
	fei_proxy_AccessVisilib.dll	[...]/bin
	fei_proxy_Data.dll	[...]/bin
	fei_proxy_LgSkeletonPolyg.dll	[...]/bin
	fei_proxy_ObjectModel.dll	[...]/bin
	fei_proxy_Process.dll	[...]/bin
	fei_proxy_ServiceHandler.dll	[...]/bin
	fei_proxy_VisilogAPI.dll	[...]/bin
	fei_proxy_VisilogIP.dll	[...]/bin
	fei_proxy_VisilogProxy.dll	[...]/bin
	fei_proxy_VlgUtil.dll	[...]/bin
	fei_proxy_boost_chrono-mt.dll	[...]/bin
	fei_proxy_boost_context-mt.dll	[...]/bin
	fei_proxy_boost_date_time-mt.dll	[...]/bin
	fei_proxy_boost_filesystem-mt.dll	[...]/bin
	fei_proxy_boost_iostreams-mt.dll	[...]/bin
	fei_proxy_boost_program_options-mt.dll	[...]/bin
	fei_proxy_boost_regex-mt.dll	[...]/bin
	fei_proxy_boost_system-mt.dll	[...]/bin
	fei_proxy_boost_thread-mt.dll	[...]/bin
	fei_proxy_documentation.dll	[...]/bin
	fei_proxy_ippro51.dll	[...]/bin
	fei_proxy_porosity.dll	[...]/bin
	fei_proxy_tbb.dll	[...]/bin
	fei_proxy_vip_jero.dll	[...]/bin
	fei_proxy_vip_magn.dll	[...]/bin
	fei_proxy_vip_nabu.dll	[...]/bin

HardCopy

If your application uses some classes in HardCopy, it requires all libraries from Open Inventor core in addition to the following ones:

Component	Windows file name	default path	comments
	fei_hardCopy.dll	[...]/bin
	fei_hardCopy_pdf.dll	[...]/bin
	fei_ifx_core.dll	[...]/bin
	fei_ifx_exporting.dll	[...]/bin
	fei_ifx_scheduling.dll	[...]/bin
	fei_hpdf.dll	[...]/bin	PDF/U3D support

IvTune

IvTune is an extension mainly designed for scene graph editing or debugging. So we do not recommend to embed any IvTune components in your application: It would be a way for the end user to change the scene graph of your application without any control.

However, we indicate below the list of files used by IvTune for your information.

Component	Windows file name	default path	comments
	fei_ivTune.dll	[...]/bin
	fei_ivTune_extender.dll	[...]/bin
	fei_ivTune_extender_base.dll	[...]/bin
	fei_ivTune_extender_inventor.dll	[...]/bin
	fei_ivTune_extender_volumeVizLDM.dll	[...]/bin
	fei_inventor_io_genericFile.dll	[...]/bin
	Qt5PrintSupport.dll	[...]/bin
	Qt5Xml.dll	[...]/bin
	IvtConfiguration.xml	OIVHOME/data/IvTune
	IvtConfiguration.xsd	OIVHOME/data/IvTune
	PerfCounter.xml	OIVHOME/data/IvTune

OpenInventor Studio

Open Inventor Studio is the alternative to IvTune when the environment variable %OIV_USE_OIVS% is 1. It is also designed for scene graph editing or debugging. So we do not recommend to embed any Open Inventor Studio components in your application: It would be a way for the end user to change the scene graph of your application without any control.

FYI: we indicate below the list of files used by Open Inventor Studio.

Component	Windows file name	default path	comments
	fei_inventor_studio.dll	[...]/bin
	fei_inventor_ui_Qt.dll	[...]/bin
	fei_scaleViz.dll	[...]/bin
	fei_hardCopy.dll	[...]/bin
	fei_common_components.dll	[...]/bin
	fei_common_models.dll	[...]/bin
	fei_common_notification_system_core.dll	[...]/bin
	fei_common_notification_system_gui.dll	[...]/bin
	fei_common_periodic_table.dll	[...]/bin
	fei_common_theme.dll	[...]/bin
	fei_common_utils.dll	[...]/bin
	Qt5PrintSupport.dll	[...]/bin
	Qt5Xml.dll	[...]/bin
	Qt5Widgets.dll	[...]/bin
	Qt5Core.dll	[...]/bin
	Qt5Gui.dll	[...]/bin
	Qt5Network.dll	[...]/bin
	Qt5Quick.dll	[...]/bin
	Qt5QmlModels.dll	[...]/bin
	Qt5Qml.dll	[...]/bin
	Qt5QuickControls2.dll	[...]/bin
	Qt5QuickWidgets.dll	[...]/bin
	Qt5Help.dll	[...]/bin
	Qt5QuickTemplates2.dll	[...]/bin
	Qt5Sql.dll	[...]/bin
	all files in qtplugins	[...]/bin/qtplugins/

DialogViz

DialogViz is an extension mainly designed for testing purpose and to write simple Open Inventor examples with a very basic GUI. So we do not suggest to embed any DialogViz components in your application.

For your information, we indicate below the list of files only used by DialogViz.

Component	Windows file name	default path	comments
	fei_dialogViz.dll	[...]/bin
	fei_inventor_ui_dialogs.dll	[...]/bin
	fei_dialogViz_qt.dll	[...]/bin