Platform and Compiler Notes - VxWorks

General Notes

• Configuring with -exceptions is necessary, because the VxWorks 6.7 g++ headers require exceptions to be enabled when compiling C++ code.
• Configure's -xplatform can be any of unsupported/vxworks-(simpentium|ppc)-(g++|dcc), but dcc (WindRiver DIAB compiler) has not yet tested been tested with Qt 4.6 and VxWorks 6.7.
• Building shared libraries with -shared (the default) doesn't really build shared libraries, like e.g. on Linux, since these are not supported by VxWorks. Instead, qmake will created partially linked objects, that can be loaded at runtime with ld.
• Creating static builds with -static is fully supported.
• "Munching" (generating constructors/destructors for static C++ objects) is done automatically by a special qmake extension (for both shared libraries and executables)
• VxWorks does not have a file system layer, but the low level storage drivers have to supply a file system like interface to the applications. Since each driver implements a different subset of the functionality supported by this interface, Qt's file system auto-tests show wildly differing results running on different "file systems". The best results can be achieved when running on a (writable) NFS mount, since that provides the most Unix-ish interface. The worst results come from the FTP file system driver, which may crash when accessed by a QFileInfo.
• Keep in mind that VxWorks doesn't call your main() function with the standard argc/argv parameters. So either add a special vxmain() function or use a tool like callmain to translate VxWorks' commandline arguments to an argc/argv array.
• Some example will fail to build, due to some missing dependencies (e.g. shared memory) - this will be fixed in a later release.