 |
VR-Forces 4.7 Class Documentation
|
All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Groups Pages
|
VR-Forces 4.7 Class Documentation
|
Please review the prerequisites for building VR-Forces in 18.2 - Prerequisites for Building VR-Forces Applications.
To build an application that uses the VR-Forces toolkit, you must let your compiler know where to find VR-Forces header files and you must let your linker know where to find VR-Forces libraries. Because VR-Forces relies on VR-Link, you must also indicate where to find VR-Link header files and libraries. In addition, when building for HLA, you must provide paths to RTI header files and libraries. Finally, there are several preprocessor definitions that must be included depending on your build configuration.
For Linux platforms, MAK provides makefiles that are configured to build the applications and the examples. Variables must be set according to vrfBuildingtheVR-ForcesApplicationforLinux. You can modify these makefiles to include additional source for your customizations.
Please review the prerequisites for building VR-Forces in vrfPrerequisitesforBuildingVR-ForcesApplications.
Under Windows, you must include paths to the VR-Forces, VR-Link, and RTI header files and libraries within your project settings. Rather than using absolute paths, we strongly recommend that you use environment variables to indicate the locations of the various components. That way, when you upgrade to new versions of VR-Link, the RTI, and so on, you will not need to change all of your project settings. In the examples we assume that MAK_VRLDIR, and MAK_RTIDIR point to your VR-Forces, VR-Link, and MAK RTI trees respectively.
For assistance, please contact technical support.
[<< Rebuilding the VR-Forces Application] [Home] [Top of Page] [Deploying VR-Forces Applications >>]