Deployment
Adding HOOPS Luminate into a Development Filetree
Once HOOPS Luminate has been installed, an easy way to extract HOOPS Luminate is to directly copy the Redsdk.m folder contents into the filetree of your own application. Redsdk.m contains everything that is needed to compile, link and run an application using HOOPS Luminate:
Bin: This is the binary folder with all the HOOPS Luminate binaries needed at runtime
Lib: This is the library folder needed at link time
Public: This is the folder that contains all header files of HOOPS Luminate, that are needed at compile time for your application
This Redsdk.m folder should be taken as a whole: each new HOOPS Luminate version will contain a new version of this folder.
Needed Libraries for Link
HOOPS Luminate has only a few binaries:
REDCore.dll (libREDCore.so on Linux, libREDCore.dylib on MacOS): This is the main HOOPS Luminate library. It contains all of the RED and RNET namespaces
REDFramework.dll (libREDFramework.so on Linux, libREDFramework.dylib on MacOS): This is an optional library that contains the RFK namespace. This is the tutorial application that can be used by the free version of HOOPS Luminate or for early prototyping steps
REDFbx.dll (libREDFbx.so on Linux, libREDFbx.dylib on MacOS): This is an optional library that contain the .FBX file import into HOOPS Luminate
Embree.dll (libembree.so on Linux x64, libembree.dylib on MacOS): This is the optional Embree library. If this library is not present, then the
RED::OPTIONS_RAY_USE_EMBREE
option value should be disabled, or HOOPS Luminate will return a error if software rendering is used
Dependencies on Windows
HOOPS Luminate requires Visual Studio 2015 redistributable package (or higher version)
REDResources.red Dependency
Some features of HOOPS Luminate depend on a REDResources.red external file. This file is provided with HOOPS Luminate next to the executables in the BuildImage/<CONFIG>/
directory, where <CONFIG> will be replaced with your platform config type.
Current features in need of this file are:
Background clouds (Adding Clouds to the Sky Texture)
The file should be placed next to the final executable. Otherwise, if a call to a function that uses it is done, an error will be thrown.