Remove outdated platform documentation

QWS does not exist anymore. If any of the other points are still relevant,
they should be re-added when the documentation is updated.

Change-Id: Ifc75dfe979627c2994a67eaed258213c59fa0517
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

1 files changed, 0 insertions, 289 deletions

diff --git a/doc/src/platforms/platform-notes-rtos.qdoc b/doc/src/platforms/platform-notes-rtos.qdoc
index d7c9aa06..a9089d9e 100644
--- a/doc/src/platforms/platform-notes-rtos.qdoc
+++ b/doc/src/platforms/platform-notes-rtos.qdoc
@@ -34,106 +34,6 @@
     \note VxWorks is a community supported platform. See the
     \l{Supported Platforms} page for more information.
 
-    This page contains information about the Qt for VxWorks port. More
-    information about the combinations of platforms and compilers supported
-    by Qt can be found on the \l{Supported Platforms} page.
-
-    \tableofcontents
-
-    \section1 Supported Versions
-
-    Qt has been tested on WindRiver VxWorks 6.7 in kernel mode using the
-    vendor supplied GCC compiler, targetting both the x86 simulator
-    (simpentium) and Power-PC devices (ppc).
-    VxWorks' RTP mode is currently not supported.
-
-    \section1 Limitations
-
-    The VxWorks kernel has an optional POSIX compatibility layer, but this
-    layer does not implement all POSIX functionality needed for a complete
-    Qt port.
-
-    \table
-    \header \li Function \li Notes
-    \row \li QProcess
-         \li Not available - VxWorks has no concept of processes.
-    \row \li QSharedMemory
-         \li Not available - VxWorks has only a global, flat address space.
-    \row \li QSystemSemaphore
-         \li Not available - VxWorks has no concept of processes.
-    \row \li QLibrary
-         \li QLibrary is only a small stub to make it possible to build
-            static plugins.
-    \row \li QCoreApplication
-         \li Can only be instantiated once. Qt's Q(CoreE)Application is
-            tightly coupled to one address space and process, while VxWorks
-            only supports one global address space and has no concept of
-            processes.
-    \endtable
-
-    \section1 Build Instructions
-
-    Qt for VxWorks needs to be \l{Cross-Compiling Qt for Embedded Linux
-    Applications}{cross-compiled} on a Linux host.  \c configure and \c make
-    the build like you would with a standard \l{Cross-Compiling Qt for
-    Embedded Linux Applications}{embedded Linux cross build}.  Building the
-    VxWorks simulator would be done like this:
-
-    \code
-    <path/to/qt/sources>/configure -xplatform unsupported/vxworks-simpentium-g++ -embedded vxworks -exceptions -no-gfx-linuxfb -no-mouse-linuxtp -no-mouse-pc -no-kbd-tty
-    make
-    \endcode
-
-    \list
-    \li \c{-xplatform unsupported/qws/vxworks-simpentium-g++} - selects the x86 simulator mkspec for VxWorks
-    \li \c{-embedded vxworks} - builds the embedded version of Qt and sets the architecture to VxWorks
-    \li \c{-exceptions} - see General Notes below
-    \li \c{-no-gfx-linuxfb}, \c{-no-mouse-linuxtp}, \c{-no-mouse-pc} and \c{-no-kbd-tty} are Linux specific and won't work on VxWorks
-    \endlist
-
-    \section1 General Notes
-
-    \list
-
-    \li Configuring with \c{-exceptions} is necessary, because the VxWorks
-    6.7 g++ headers require exceptions to be enabled when compiling C++
-    code.
-
-    \li Configure's \c{-xplatform} can be any of
-    \c{unsupported/vxworks-(simpentium|ppc)-(g++|dcc)}, but \c{dcc}
-    (WindRiver DIAB compiler) has not yet tested been tested with Qt 4.6 and
-    VxWorks 6.7.
-
-    \li Building shared libraries with \c{-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 \c{ld}.
-
-    \li Creating static builds with \c{-static} is fully supported.
-
-    \li "Munching" (generating constructors/destructors for static C++
-    objects) is done automatically by a special qmake extension (for both
-    shared libraries and executables)
-
-    \li 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
-    \c{QFileInfo}.
-
-    \li Keep in mind that VxWorks doesn't call your \c{main()} function with
-    the standard \c{argc}/\c{argv} parameters.  So either add a special
-    \c{vxmain()} function or use a tool like \c{callmain} to translate
-    VxWorks' commandline arguments to an \c{argc}/\c{argv} array.
-
-    \li Some example will fail to build, due to some missing dependencies
-    (e.g. shared memory) - this will be fixed in a later release.
-
-    \endlist
 */
 
 /*!
@@ -145,95 +45,6 @@
     \note QNX is a community supported platform. See the
     \l{Supported Platforms} page for more information.
 
-    This page contains information about the Qt for QNX port. More
-    information about the combinations of platforms and compilers supported
-    by Qt can be found on the \l{Supported Platforms} page.
-
-    Note that Qt for QNX is currently based on \l{Qt for Embedded Linux}, which
-    contains its own windowing system. Mixing QNX's Photon environment with
-    Qt for QNX is currently not possible. Building Qt for QNX with Photon's
-    X11 embedded server is not recommended due to missing support for X11 extensions,
-    resulting in poor rendering quality.
-
-    Qt for QNX contains experimental screen and input drivers based on QNX's
-    \c devi-hid and \c io-display. For more information, check the class documentation
-    for QQnxScreen, QWSQnxKeyboardHandler and QQnxMouseHandler. See the
-    \l{Porting Qt for Embedded Linux to a New Architecture} document for information
-    on how to add custom screen or input drivers.
-
-    \tableofcontents
-
-    \section1 Supported Versions
-
-    Qt has been tested on QNX 6.4 on i386 and PowerPC targets with QNX's default
-    gcc compiler.
-
-    \section1 Limitations
-
-    Some of Qt's functionality is currently not available on QNX:
-
-    \table
-    \header \li Function \li Notes
-    \row \li QProcess
-         \li Not available - QNX doesn't support mixing threads and processes.
-    \row \li QSharedMemory
-         \li Not available - QNX doesn't support SYSV style shared memory.
-    \row \li QSystemSemaphore
-         \li Not available - QNX doesn't support SYSV style system semaphores.
-    \row \li QWS Multi Process
-         \li QT_NO_QWS_MULTIPROCESS is always on due to missing shared memory support.
-    \endtable
-
-    \section1 Build Instructions
-
-    Qt for QNX needs to be built either on a QNX system, or \l{Cross-Compiling Qt
-    for Embedded Linux Applications}{cross-compiled} on a Linux host. In either
-    case, The QNX Software Development Platform must be installed.
-
-    Example configure line for cross-compiling Qt for QNX on a Linux host for an
-    i386 QNX target:
-
-    \code
-    configure -xplatform unsupported/qws/qnx-i386-g++ -embedded i386 -no-gfx-linuxfb -no-mouse-linuxtp -no-kbd-tty -qt-gfx-qnx -qt-mouse-qnx -qt-kbd-qnx -no-exceptions
-    \endcode
-
-    \list
-    \li \c{-xplatform unsupported/qws/qnx-i386-g++} - selects the i386-g++ mkspec for QNX
-    \li \c{-embedded i386} - builds the embedded version of Qt and sets the architecture to i386
-    \li \c{-no-gfx-linuxfb},  \c{-no-mouse-linuxtp} and \c{-no-kbd-tty} are Linux specific and won't work on QNX
-    \li \c{-no-exceptions} - reduces the size of the library by disabling exception support
-    \li \c{-qt-gfx-qnx} - enables the experimental \c{io-graphics} based display driver
-    \li \c{-qt-mouse-qnx} - enables the experimental \c{devi-hig} based mouse driver
-    \li \c{-qt-kbd-qnx} - enables the experimental \c{devi-hig} based keyboard driver
-    \endlist
-
-    \section1 General Notes
-
-    \list
-    \li To enable the experimental QNX display and input drivers, \c{io-display} needs to be
-       up and running. The \c devi-hid based Qt input drivers require \c devi-hid to run
-       in resource mode without Photon support. To enable a standard mouse and keyboard
-       combination, run \c devi-hid as follows: \c{/usr/photon/bin/devi-hid -Pr kbd mouse}.
-       Note that your current shell will not accept keyboard and mouse input anymore after
-       running that command, so run it either from a script that launches a Qt application
-       afterwards, or make sure to have remote login available to launch a Qt application.
-       In addition, the \c QWS_DISPLAY, \c QWS_MOUSE_PROTO and \c QWS_KEYBOARD environment
-       variables should all be set to \c{qnx} before running a Qt application.
-
-    \li The 3rd party TIFF library currently doesn't build due to the missing \c inflateSync
-       symbol from QNX's \c{libz.so.2}. Workarounds would be to manually replace QNX's libz
-       with a newer version, or disable the TIFF plugin entierly by appending
-       \c{QT_CONFIG += no-tiff} to \c{.qmake.cache} after configuring Qt.
-
-    \li Some of the tools and examples do not compile due to dependencies on QProcess
-       or other classes that are not available on QNX.
-    \endlist
-
-    \section1 Platform Regressions
-
-    Qt for QNX's behavior is mostly identical with \l{Qt for Embedded Linux}. However,
-    some regressions were spotted in QDateTime computation around year 0 and year 1970,
-    which have been tracked back to faulty time zone data on some QNX versions.
 */
 
 /*!
@@ -245,104 +56,4 @@
     \note INTEGRITY is a community supported platform. See the
     \l{Supported Platforms} page for more information.
 
-    This page contains information about the Qt for INTEGRITY port. More
-    information about the combinations of platforms and compilers supported
-    by Qt can be found on the \l{Supported Platforms} page.
-
-    Note that Qt for INTEGRITY is currently based on \l{Qt for Embedded Linux},
-    which contains its own windowing system.
-
-    Qt for INTEGRITY contains experimental screen and input drivers based on the
-    gh_FB Framebuffer API for graphics, a Connection-based mouse and keyboard
-    support. For information about these drivers, please refer to Green Hills
-    Software standard support.
-
-    \tableofcontents
-
-    \section1 Supported Versions
-
-    Qt has been tested on INTEGRITY 10 on various PowerPC, ARM and x86 targets.
-    On some platforms a native graphics FrameBuffer driver is available and has
-    then been used for testing. On all other platforms, the default FrameBuffer
-    VNC driver is used.
-
-    \section1 Limitations
-
-    Some of Qt's functionality is currently not available on INTEGRITY:
-
-    \table
-    \header \li Function \li Notes
-    \row \li QProcess
-         \li Not implemented. Volunteers welcome.
-    \row \li QSharedMemory
-         \li Not available - INTEGRITY doesn't support SYSV style shared memory.
-    \row \li QSystemSemaphore
-         \li Not available - INTEGRITY doesn't support SYSV style system semaphores.
-    \row \li QWS Multi Process
-         \li QT_NO_QWS_MULTIPROCESS is always on due to missing shared memory support.
-    \row \li QtScript
-         \li Not available - INTEGRITY's mmap() doesn't support allocating memory.
-    \endtable
-
-    \section1 Build Instructions
-
-    Qt for INTEGRITY can be built on either a Linux or Windows (with cygwin) host.
-    In both cases, a standard installation of INTEGRITY is required, with the
-    addition of the FrameBuffer API.
-
-    Example configure line for cross-compiling Qt for INTEGRITY for an
-    ARM INTEGRITY target:
-
-    \code
-    ./configure --hostprefix=$PWD -embedded integrity -xplatform unsupported/qws/integrity-arm-cxarm -static -qt-kbd-integrity -qt-mouse-integrity -no-mouse-linuxtp -no-mouse-pc -no-kbd-tty -qt-gfx-integrityfb -no-gfx-linuxfb -no-glib -no-openssl -no-largefile -little-endian -arch integrity -prefix / -opensource -no-feature-QWS_MULTIPROCESS -no-feature-SHAREDMEMORY -no-feature-PROCESS -no-feature-SYSTEMSEMAPHORE -no-feature-PRINTER -no-feature-QWS_QPF2 -no-libtiff -no-exceptions -no-scripttools
-    \endcode
-
-    \list
-    \li \c{--hostprefix=$PWD} - specifies the current directory as the base source for Qt
-    \li \c{-arch integrity} - sets the architecture to INTEGRITY (for atomic operations)
-    \li \c{-embedded integrity} - builds the embedded version of Qt and sets the architecture to INTEGRITY
-    \li \c{-xplatform unsupported/qws/integrity-arm-cxarm} - selects the arm-cxarm mkspec for INTEGRITY
-    \li \c{-static} - specifies a static build of Qt
-    \li \c{-no-gfx-linuxfb},  \c{-no-mouse-linuxtp}, \c{-no-mouse-pc} and \c{-no-kbd-tty} are Linux specific and won't work on INTEGRITY
-    \li \c{-no-exceptions} - reduces the size of the library by disabling exception support
-    \li \c{-no-openssl} - disable support for OpenSSL
-    \li \c(-no-libtiff} - disable support for libTIFF
-    \li \c{-no-glib} - disable support for unavailable Glib
-    \li \c{-no-largefile} - disable support for large (> 2TB) files
-    \li \c{-no-scripttools} - disable support for QtScript tools
-    \li \c{-qt-gfx-integrity} - enables the experimental gh_FB based display driver
-    \li \c{-qt-mouse-integrity} - enables the experimental Connection-based mouse driver
-    \li \c{-qt-kbd-integrity} - enables the experimental Connection-based keyboard driver
-    \endlist
-
-    The above script will generate MULTI .gpj Project files, not Makefiles. The
-    main benefit of using these project files is automatic dependency checking,
-    but this also provides an organization known to INTEGRITY customers.
-    For Qt libraries, the top-level file is projects.gpj.
-
-    \section1 General Notes
-
-    \list
-    \li Before you run the above configure line, you may want to modify the values
-       of INTEGRITY_DIR and INTEGRITY_BSP in unsupported/qws/integrity-arm-cxarm/qmake.conf.
-       If you do not do this, you will have to modify the resulting generated projects.gpj
-
-    \li Compilation of native preprocessing tools (moc, rcc, uic) is not automatic. From
-       a Linux shell or a MingWin shell, you can run the following command to compile these tools :
-       \code
-       cd src/tools/bootstrap && make && cd ../rcc && make && cd ../moc && make && cd ../uic && make && cd ../../..
-       \endcode
-
-    \li GIF and TIFF support are currently not enabled.
-
-    \li Default .int files are generated. You may want to modify the amount of heap assigned
-       to each example by modifying the HeapSize declaration in the specific example .int file.
-
-    \li Some of the tools and examples do not compile due to dependencies on QProcess
-       or other classes that are not available on INTEGRITY.
-
-    \endlist
-
-    \section1 Platform Regressions
-
 */