 |
VR-Forces Developer's Guide
|
All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Groups Pages
|
VR-Forces Developer's Guide
|
This section describes issues specific to the use of the Boost library.
For complete Boost documentation, please got to its web site: http://www.boost.org/
The latest versions of Boost include Windows.h, which redefines the min and max macros. The macros cause compile time problems with the standard library implementation. The temporary solution is to disable Windows.h and redefine the macros using the NOMINMAX macro. This is typically done in the Preprocessor settings for all projects.
Signals and slots are a way of communicating between objects. An object can emit a signal representing some event and any number of objects can receive the signal. Boost and Qt both use signals. The GUI API uses Qt signals in the GUI and Boost signals everyplace else.
Unfortunately Qt defines a macro that conflicts with the Boost signals namespace. Boost has a workaround in which it creates a namespace alias. VR-Forces provides a header, signalslib.h, that implements this workaround. To use it, include signalslib.h in any file that uses both Qt and Boost signals before any Qt header. vrvCoreQt and all other VR-Forces Qt libraries do this automatically, so most developers will not need to do this.
When you compile using Boost, you must add the following preprocessor flags:
[<< The Qt Toolkit] [Home] [Top of Page] [Building VR-Forces Applications and Examples >>]