diff --git a/doc/src/images/kernel-settings.png b/doc/src/images/kernel-settings.png
new file mode 100644
index 0000000000000000000000000000000000000000..36cb747ff905af085b0f9fcb0db3cf3c15e720bc
Binary files /dev/null and b/doc/src/images/kernel-settings.png differ
diff --git a/doc/src/images/open-project.PNG b/doc/src/images/open-project.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..18a1af52b2aa3cb780184ae1625a6e2fd57606ed
Binary files /dev/null and b/doc/src/images/open-project.PNG differ
diff --git a/doc/src/images/project-view-2.png b/doc/src/images/project-view-2.png
new file mode 100644
index 0000000000000000000000000000000000000000..2f68420e31582b0c1ebacb2d434562635387d02f
Binary files /dev/null and b/doc/src/images/project-view-2.png differ
diff --git a/doc/src/images/project-view.png b/doc/src/images/project-view.png
new file mode 100644
index 0000000000000000000000000000000000000000..cf540226556d79bdbede260ae9b79dc6ecb6fff2
Binary files /dev/null and b/doc/src/images/project-view.png differ
diff --git a/doc/src/images/project-wizard.PNG b/doc/src/images/project-wizard.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..fec0ea45e8cec63644c10b64101c947988dd26b6
Binary files /dev/null and b/doc/src/images/project-wizard.PNG differ
diff --git a/doc/src/images/select-item-to-add.png b/doc/src/images/select-item-to-add.png
new file mode 100644
index 0000000000000000000000000000000000000000..9dcdd83b8201c56b6f25f321b18b0e0e6c03834f
Binary files /dev/null and b/doc/src/images/select-item-to-add.png differ
diff --git a/doc/src/images/vas-galcore.PNG b/doc/src/images/vas-galcore.PNG
new file mode 100644
index 0000000000000000000000000000000000000000..d635809a724168e63a14979b2ab5681cd65c64ba
Binary files /dev/null and b/doc/src/images/vas-galcore.PNG differ
diff --git a/doc/src/platforms/integrity-build-monolith-app-tutorial.qdoc b/doc/src/platforms/integrity-build-monolith-app-tutorial.qdoc
new file mode 100644
index 0000000000000000000000000000000000000000..b7d5a9ecee074c9300dc36fc0677799050f716ee
--- /dev/null
+++ b/doc/src/platforms/integrity-build-monolith-app-tutorial.qdoc
@@ -0,0 +1,243 @@
+/****************************************************************************
+**
+** Copyright (C) 2017 The Qt Company Ltd.
+** Contact: https://www.qt.io/licensing/
+**
+** This file is part of the documentation of the Qt Toolkit.
+**
+** $QT_BEGIN_LICENSE:FDL$
+** Commercial License Usage
+** Licensees holding valid commercial Qt licenses may use this file in
+** accordance with the commercial license agreement provided with the
+** Software or, alternatively, in accordance with the terms contained in
+** a written agreement between you and The Qt Company. For licensing terms
+** and conditions see https://www.qt.io/terms-conditions. For further
+** information use the contact form at https://www.qt.io/contact-us.
+**
+** GNU Free Documentation License Usage
+** Alternatively, this file may be used under the terms of the GNU Free
+** Documentation License version 1.3 as published by the Free Software
+** Foundation and appearing in the file included in the packaging of
+** this file. Please review the following information to ensure
+** the GNU Free Documentation License version 1.3 requirements
+** will be met: https://www.gnu.org/licenses/fdl-1.3.html.
+** $QT_END_LICENSE$
+**
+****************************************************************************/
+
+
+/*!
+ \page integrity-monolith-project-tutorial.html
+ \title Qt for INTEGRITY: Monolith Project Tutorial
+ \previouspage platform-notes-integrity.html
+ \nextpage integrity-installing-dependencies.html
+
+ The INTEGRITY applications can be monolith application projects,
+ dynamic download application projects, or kernelspace projects. The monolith
+ application is a stand-alone executable that you can run directly on a
+ target device.
+
+ In this tutorial, we build an INTEGRITY monolith project of
+ the Qt application. We also create a bootable SD card, so you can run
+ your application in the i.MX6 Quad board. After following the steps in this
+ tutorial, you will have the Qt for INTEGRITY development environment up and running.
+
+ The tutorial assumes you have the
+ \l {https://boundarydevices.com/product/sabre-lite-imx6-sbc/}
+ {i.MX6 Quad board} with a micro SD card.
+
+ Tutorial content:
+ \list 1
+ \li \l {Installing Platform Dependencies}
+ \li \l {Preparing BSP for i.MX6 Quad Board}
+ \li \l {Building Qt for i.MX6 Quad Board}
+ \li \l {Building Monolith Project}
+ \li \l {Building U-Boot Image}
+ \li \l {Creating Bootable SD card}
+ \li \l {Preparing U-Boot}
+ \endlist
+
+*/
+
+/*!
+ \page integrity-installing-dependencies.html
+ \title Installing Platform Dependencies
+ \previouspage integrity-monolith-project-tutorial.html
+ \nextpage integrity-preparing-bsp-for-imx6quad-board.html
+
+ Before you can build the applications with Qt for INTEGRITY,
+ you must have the correct build tools and other dependencies installed
+ in the 64-bit Linux development host:
+
+ \table 80%
+ \header \li Requirement \li Description
+ \row \li An INTEGRITY 11.4.4 installation
+ \li Installation must contain the patches for C++11 support.
+ Contact \l {https://support.ghs.com/contact/request-support/}
+ {Green Hills Software}.
+ \row \li MULTI IDE and Green Hills Software Compiler (version 2016.5.4 or newer)
+ \li The Green Hills Software development tools. See
+ \l {http://www.ghs.com/products/MULTI_IDE.html} {MULTI IDE}.
+ For licenses, contact \l {https://support.ghs.com/licensing/request-license/}
+ {Green Hills Software}.
+ \note You need to get an additional patch from Green Hills Software.
+ \row
+ \li An ELF (Executable and Linkable Format) loader compatible with a device tree
+ \li Part of the Green Hills Software development tools.
+ \row
+ \li The U-Boot tools
+ \li Universal Boot Loader (U-Boot) is used in the embedded devices to
+ package the instructions to boot the device's operating system kernel.
+ \note Especially \c mkimage is required.
+ \row
+ \li Perl programming language
+ \li Required if you are getting the Qt 5 sources via the Git version control system.
+ See \l {https://www.perl.org/get.html}.
+ \note Perl is not required if you download the Qt sources via
+ your Qt Account.
+ \endtable
+*/
+
+/*!
+ \page integrity-preparing-bsp-for-imx6quad-board.html
+ \title Preparing BSP for i.MX6 Quad Board
+ \previouspage integrity-installing-dependencies.html
+ \nextpage integrity-building-qt-for-imx6quad-board.html
+
+ With MULTI Launcher, you can prepare the board support package (BSP)
+ for i.MX6 Quad board:
+
+ \list 1
+ \li Start MULTI Launcher.
+ \li Start Project Manager by selecting \uicontrol {Components} >
+ \uicontrol {Open Project Manager}.
+ \li In your INTEGRITY installation, select the project file \e {default.gpj}
+ under the \e {platform-cortex-a9} folder:
+
+ \image open-project
+
+ \li Select \uicontrol {Open}.
+ \endlist
+
+ In the MULTI Project Manager view, you see a tree structure of the opened
+ project.
+
+ Clean \e {default.gpj} and build the projects:
+
+ \list 1
+ \li Select \uicontrol {Build} > \uicontrol {Clean default.gpj}.
+ \li Select the files \e {system_libs.gpj}, \e {bsp_libs.gpj}, and
+ \e {kernel.gpj} one by one, and select \uicontrol {Build} >
+ \uicontrol {Build Project <file name>} for each selected file.
+ \endlist
+
+ Preparation for the board support package is now done.
+*/
+
+/*!
+ \page integrity-building-qt-for-imx6quad-board.html
+ \title Building Qt for i.MX6 Quad Board
+ \previouspage integrity-preparing-bsp-for-imx6quad-board.html
+ \nextpage integrity-building-monolith.html
+
+ \include integrity-building-qt-imx6.qdocinc building qt for imx6quad
+*/
+
+/*!
+ \page integrity-building-monolith.html
+ \title Building Monolith Project
+ \previouspage integrity-building-qt-for-imx6quad-board.html
+ \nextpage integrity-building-u-boot-image.html
+
+ \include integrity-building-monolith.qdocinc building monolith
+*/
+
+/*!
+ \page integrity-building-u-boot-image.html
+ \title Building U-Boot Image
+ \previouspage integrity-building-monolith.html
+ \nextpage integrity-creating-bootable-sd-card.html
+
+ To build a U-Boot image, open a terminal and navigate to the project
+ directory created in \l {Building Monolith Project}. In our example the
+ project directory is \e {mymonolith}.
+
+ Under the project directory, you will find an executable with the same name
+ you gave to your monolith in \l {Project Manager Settings}.
+ In our example the executable name is \e {myproject}.
+
+ Run the \c elfloader command for the executable. You will find the \c elfloader
+ command under your compiler directory:
+
+ \badcode
+ john@doe: /usr/ghs/comp_201654/elfloader -l /usr/ghs/int1144/util/elfloader/cortexa9_elfloader.bin -o myproject.elf myproject
+ \endcode
+
+ The example \c elfloader command above assumes your Green Hills Software (GHS)
+ compiler is version 2016.5.4, and your INTEGRITY and GHS compiler
+ installations are found from their default locations. However, you can
+ modify the paths in the example according to your configuration.
+
+ Finally, build the U-Boot image with the \c mkimage tool.
+ The last argument in the \c mkimage command specifies the U-Boot image name.
+ In the example below, we use the name \e {demo.image}.
+ To invoke \c mkimage, run the following command in a terminal:
+
+ \badcode
+ john@doe: mkimage -A arm -O linux -T kernel -C none -a 20000000 -e 20000000 -n INTEGRITY+Qt -d myproject.elf demo.image
+ \endcode
+*/
+
+/*!
+ \page integrity-creating-bootable-sd-card.html
+ \title Creating Bootable SD Card
+ \previouspage integrity-building-u-boot-image.html
+ \nextpage integrity-preparing-u-boot.html
+
+ With a bootable micro SD card your i.MX6 Quad board can run the INTEGRITY
+ monolith application on the board. To create the bootable SD card:
+
+ \list 1
+ \li Format the SD card with a FAT32 filesystem.
+ \li Save the \e {demo.image} file (built with \c mkimage in
+ \l {Building U-Boot Image}) and the device tree blob file
+ \e {imx6q-sabrelite.dtb} for the i.MX6 Quad board under your SD card root.
+ \note You will find the device tree blob file in your INTEGRITY installation,
+ under the path
+ /usr/ghs/int1144/platform-cortex-a9/imx6-sabrelite/imx6q-sabrelite.dtb.
+ \li Set the SD card into your i.MX6 Quad board.
+ \endlist
+
+*/
+
+/*!
+ \page integrity-preparing-u-boot.html
+ \title Preparing U-Boot
+ \previouspage integrity-creating-bootable-sd-card.html
+ \nextpage integrity-monolith-project-tutorial.html
+
+ Finally, prepare the i.MX6 Quad board for U-Boot:
+
+ \list 1
+ \li Connect to your i.MX6 Quad board with a serial connection at a baud rate of
+ 115200.
+ \li Set the following environment variables in the U-Boot terminal:
+
+ \badcode
+ setenv bootcmd_demo_dt 'mmc dev 1;
+ fatload mmc 1:1 20000000 demo.image;
+ fatload mmc 1:1 4FFE0000 imx6q-sabrelite.dtb;
+ bootm 20000000 - 4FFE0000'
+
+ setenv bootcmd 'run bootcmd_demo_dt'
+ saveenv
+ \endcode
+
+ \note The file \e {demo.image} was built with the mkimage tool in
+ \l {Building U-Boot Image}.
+
+ \li Reset the i.MX6 Quad board.
+ \endlist
+
+ Now your i.MX6 Quad board is ready to run your application.
+*/
diff --git a/doc/src/platforms/integrity-building-monolith.qdocinc b/doc/src/platforms/integrity-building-monolith.qdocinc
new file mode 100644
index 0000000000000000000000000000000000000000..c89a05b58e501f4f4bcebf7fe8e40a2c113c8235
--- /dev/null
+++ b/doc/src/platforms/integrity-building-monolith.qdocinc
@@ -0,0 +1,360 @@
+/****************************************************************************
+**
+** Copyright (C) 2017 The Qt Company Ltd.
+** Contact: https://www.qt.io/licensing/
+**
+** This file is part of the documentation of the Qt Toolkit.
+**
+** $QT_BEGIN_LICENSE:FDL$
+** Commercial License Usage
+** Licensees holding valid commercial Qt licenses may use this file in
+** accordance with the commercial license agreement provided with the
+** Software or, alternatively, in accordance with the terms contained in
+** a written agreement between you and The Qt Company. For licensing terms
+** and conditions see https://www.qt.io/terms-conditions. For further
+** information use the contact form at https://www.qt.io/contact-us.
+**
+** GNU Free Documentation License Usage
+** Alternatively, this file may be used under the terms of the GNU Free
+** Documentation License version 1.3 as published by the Free Software
+** Foundation and appearing in the file included in the packaging of
+** this file. Please review the following information to ensure
+** the GNU Free Documentation License version 1.3 requirements
+** will be met: https://www.gnu.org/licenses/fdl-1.3.html.
+** $QT_END_LICENSE$
+**
+****************************************************************************/
+/*!
+//! [building monolith]
+
+ In this tutorial, we build a monolith INTEGRITY project for a Qt example
+ application. You can select any Qt example application that uses the
+ \l {Supported Qt Modules} {supported Qt modules}.
+
+ Before you can build a monolith INTEGRITY project, you need to prepare your
+ build environment for the \c qmake build tool. You can do this by running
+ the script \e {~/setEnvironment.sh} that you created in
+ \l {Creating Script for Running Exports}.
+
+ Run the following commands in a terminal:
+
+ \badcode
+ source ~/setEnvironment.sh
+ <Qt installation path>/qtbase/bin/qmake <Qt example application path>/<projectname>.pro
+ make
+ \endcode
+
+ The \c qmake tool must be called under the Qt installation path
+ (<Qt installation path>), where you installed the Qt sources in
+ \l {Getting Qt Source Code}.
+
+ <Qt example application path>/<projectname>.pro is the installation path of
+ the Qt example application project file that the monolith INTEGRITY project
+ will be built for.
+
+ \section1 Building Monolith Project
+
+ To build a monolith INTEGRITY project, create an empty directory for your
+ project in your home folder. In the steps below, we use the directory name
+ \e {mymonolith}.
+
+ \section2 Defining Project with Project Wizard
+
+ Launch MULTI Launcher and select \uicontrol {File} > \uicontrol
+ {Create New Project}. Define your monolith project with Project Wizard:
+
+ \list 1
+ \li In the \uicontrol {Project name} tab, fill in the \uicontrol {Directory}
+ field with the directory you just created.
+ \li Select \uicontrol {Next}.
+ \li In the \uicontrol {Operating System} tab, select \e {INTEGRITY}
+ from the \uicontrol {Operating System} list.
+ \note The \uicontrol {OS Distribution Directory} field must contain your
+ INTEGRITY installation directory (in our example, \e{mymonolith}).
+ \li Select \uicontrol {Next}.
+ \li In the \uicontrol {Processor Family} tab, select \uicontrol {ARM}.
+ \li Select \uicontrol {Next}.
+ \li In the \uicontrol {Target Board} tab, select \uicontrol {ARM Cortex-A9 Platform }
+ from the target board list.
+ \li Select \uicontrol {Finish}.
+ \endlist
+
+ \image project-wizard
+
+ After selecting \uicontrol {Finish} in Project Wizard, Project Manager is
+ opened.
+
+ \section2 Project Manager Settings
+
+ With Project Manager you can define the settings for the monolith project:
+
+ \list 1
+ \li In the \uicontrol {Select Item to Add} dialog page, select \uicontrol
+ {Monolith} from the \uicontrol {Create New} list.
+
+ \image select-item-to-add
+
+ \li Select \uicontrol {Next}.
+ \li In the \uicontrol {Settings for Monolith} dialog, define the settings:
+ \list
+ \li \uicontrol {Source Code Directory} is your project directory
+ (in our example, \e {mymonolith}).
+ \li \uicontrol {Project Name} is the name of your project. In our
+ example, we use the name \e{myproject}.
+ \li \uicontrol {Language} must be \uicontrol {C}. The Qt projects are
+ C++ projects, but this will be configured later.
+ \li Select \uicontrol {Next}.
+ \li \uicontrol {Use Shared Libraries} should not be selected.
+ \li Select \uicontrol {Next}.
+ \endlist
+ \li In the \uicontrol {Configure number of Virtual AddressSpaces} dialog
+ page, select the checkbox \uicontrol {Names of Virtual Address Spaces} and
+ type \e{galcore}.
+ \li Select \uicontrol {Next}.
+ \li In the \uicontrol {Settings for Kernel} dialog page, type the name of
+ your kernel.
+ \li Select \uicontrol {Debugging}, \uicontrol {Dynamic Load} and
+ \uicontrol {ResourceManager} from the \uicontrol {Kernel Libraries} list.
+
+ \image kernel-settings
+
+ \li Select \uicontrol {Next}.
+ \li In the \uicontrol {Settings for OS Module Selection} dialog page,
+ select \uicontrol {File System (User Configured)} and \uicontrol
+ {GHnet IPv4 Stack (Virtual)} from the \uicontrol {OS Module} list.
+ \li Select \uicontrol {Next}.
+ \li In the \uicontrol {Settings for File System (User Configured)} dialog
+ page, select a filesystem that your monolith project supports.
+
+ In our example, we have selected \uicontrol {MSDOS FAT} from the
+ \uicontrol {Libraries} list.
+ \li Select \uicontrol {Finish}.
+ \li In the \uicontrol {Settings for Add File System Clients} dialog page,
+ select \uicontrol {Finish}.
+ \endlist
+
+ \section2 Adding File System Mount Point
+
+ You need to configure the file system to use the first partition of the
+ micro SD card. In the MULTI Project Manager view, you see a tree structure
+ of your monolith project:
+
+ \list 1
+ \li Right-click the file \e {mounttable.c} to open the context menu.
+ \li Select \uicontrol {Modify Project} >
+ \uicontrol {Add INTEGRITY File System Mount Point}.
+ \li In the \uicontrol {Settings for FS MountPoint} dialog, define
+ the settings:
+ \list
+ \li Type \e {/} to \uicontrol {Mount Directory}.
+ \li Select \uicontrol {Next}.
+ \li \uicontrol {File System Type} is \e {MSDOS FAT}.
+ \li Select \uicontrol {Next}.
+ \li Select the \uicontrol {Use Physical Device} radio button.
+ \li Type \e {SDCardDev1} to the \uicontrol {Device} field.
+ \li \uicontrol {Slice} is \e {a}.
+ \li Select \uicontrol {Finish}.
+ \endlist
+ \endlist
+
+ \section2 Galcore VAS Settings
+
+ Next, define the virtual address space (VAS) settings for your project.
+
+ In the MULTI Project Manager view, you see a tree structure of your monolith
+ project:
+
+ \list 1
+ \li Double-click the .int file in your project (1) (in the steps below,
+ \e {myproject.int}).
+ \li In the opened window, double-click the galcore virtual address
+ space (VAS) area (2).
+
+ \image project-view
+
+ \li \uicontrol {VirtualAddressSpace Options} dialog is opened.
+ \li In the \uicontrol {Attributes} tab, select the values defined in
+ \l {Values in Attributes Tab}.
+ \li Select \uicontrol {OK}.
+ \li In the galcore virtual address space area, double-click the
+ \uicontrol {Task Initial} area (3).
+
+ \image project-view-2
+
+ \li Select the \uicontrol {Start Automatically} check box.
+ \li Select \uicontrol {OK}.
+ \endlist
+
+ \section3 Values in Attributes Tab
+
+ Add the following attribute values for the virtual address space:
+
+ \table 80%
+ \header \li Attribute \li Value
+ \row
+ \li Maximum Priority
+ \li 255
+ \row
+ \li Maximum Weight
+ \li 255
+ \row
+ \li Memory Pool Size
+ \li 2000P
+ \row
+ \li Heap Size
+ \li 0X2000000
+ \row
+ \li Heap Extension Reserved Size
+ \li 0x20000
+ \row
+ \li Arguments
+ \li Leave blank.
+ \header \li Checkbox \li Value
+ \row
+ \li Create Extra Virtual Memory Regions
+ \li Select the checkbox.
+ \endtable
+
+ \section2 Editing Galcore Project
+
+ You need to edit a number of files in the monolith project.
+
+ \section3 File galcore.c
+
+ \list 1
+ \li Select \e{galcore.c} from the tree structure in the MULTI Project
+ Manager view.
+ \li Double-click the file to open it for editing.
+ \li Add the following code to \e{galcore.c}:
+
+ \badcode
+ #include <INTEGRITY.h>
+ #include <stdlib.h>
+ #include <stdio.h>
+ extern Error GalCore_TaskInit(void);
+ int main(void) {
+ Error E;
+ E = GalCore_TaskInit();
+ if (E != Success) {
+ printf("Failed to start GalCore tasks\n");
+ }
+ Exit(0);
+ }
+ \endcode
+ \endlist
+
+ \section3 File galcore.gpj
+
+ \list 1
+ \li Select \e{galcore.gpj} from the tree structure in the MULTI Project
+ Manager view.
+ \li Right-click the file to open the context menu.
+ \li Select \uicontrol{Edit}.
+ \li Add the file \e{libgalcore.a} to \e{galcore.gpj}.
+ \endlist
+
+ Contents of \e{galcore.gpj} should be as follows:
+
+ \badcode
+ #!gbuild
+ #component integrity_virtual_address_space
+ [Program]
+ -lgalcore
+ tgt/INTEGRITY.ld
+ galcore.c
+ \endcode
+
+ \section3 File kernel.gpj
+
+ \list 1
+ \li Select \e{kernel.gpj} from the tree structure in the MULTI Project
+ Manager view.
+ \li Right-click the file to open the context menu.
+ \li Select \uicontrol{Edit}.
+ \li Add the file \e{libgalcore-iod.a} to \e{kernel.gpj}.
+ \endlist
+
+ Contents of \e{kernel.gpj} should be as follows:
+
+ \badcode
+ #!gbuild
+ #component integrity_kernel_monolith
+ [Program]
+ -kernel
+ -ldebug
+ -lload
+ -lres
+ -lgalcore-iod
+ tgt/default.ld
+ myproject_kernel.c
+ global_table.c
+ \endcode
+
+ \section3 File monolith.gpj
+
+ \list 1
+ \li Select \e{monolith.gpj} from the tree structure in the MULTI Project
+ Manager view.
+ \li Righ-click the file to open the context menu.
+ \li Select \uicontrol{Edit}.
+ \li Add the additional library directory \e {$(__LIBS_DIR_BASE)/Vivante}.
+ \endlist
+
+ Contents of \e{monolith.gpj} should be as follows:
+
+ \badcode
+ #!gbuild
+ #component integrity_monolith
+ [INTEGRITY Application]
+ -non_shared
+ -I$__OS_DIR/modules/ghs/ghnet2/source/kernel/integrity/ip4server :sourceDir=$__OS_DIR/modules/ghs/ghnet2/source/kernel/integrity/ip4server
+ -L$(__LIBS_DIR_BASE)/Vivante
+ tgt/default.bsp
+ myproject.int
+ galcore.gpj [Program]
+ myproject_kernel.gpj [Program]
+ my_ivfsserver_module.gpj [Program]
+ ip4server_module.gpj [Program]
+ \endcode
+
+ \section3 .int File
+
+ \list 1
+ \li Select the \e {.int} file of your project from the tree structure in the MULTI Project
+ Manager view.
+ \li Right-click the file to open the context menu.
+ \li Select \uicontrol{Edit}.
+ \li Add the following lines at the end of the file.
+
+ \note Replace </path/to/your/app/executable> with a path to your application executable.
+
+ \badcode
+ AddressSpace
+ Name myappname
+ Filename /path/to/your/app/executable
+ MemoryPoolSize 0x2000000
+ Language C++
+ HeapSize 0x6000000
+
+ Task Initial
+ StackSize 0x30000
+ StartIt true
+ EndTask
+ HeapExtensionReservedSize 0x2000000
+ EndAddressSpace
+ \endcode
+ \endlist
+
+ \section2 Building monolith.gpj
+
+ Open \e{monolith.gpj} from the tree structure in the MULTI Project Manager
+ view. To build the project:
+
+ \list 1
+ \li Right-click \e{monolith.gpj} to open the context menu.
+ \li Select \uicontrol{Build}.
+ \endlist
+
+ Your monolith project is now ready to be packaged for U-Boot.
+//! [building monolith]
+*/
diff --git a/doc/src/platforms/integrity-building-qt-imx6.qdocinc b/doc/src/platforms/integrity-building-qt-imx6.qdocinc
new file mode 100644
index 0000000000000000000000000000000000000000..37a203284c2172ccd6424e2fcdd6840d3f75184f
--- /dev/null
+++ b/doc/src/platforms/integrity-building-qt-imx6.qdocinc
@@ -0,0 +1,141 @@
+/****************************************************************************
+**
+** Copyright (C) 2017 The Qt Company Ltd.
+** Contact: https://www.qt.io/licensing/
+**
+** This file is part of the documentation of the Qt Toolkit.
+**
+** $QT_BEGIN_LICENSE:FDL$
+** Commercial License Usage
+** Licensees holding valid commercial Qt licenses may use this file in
+** accordance with the commercial license agreement provided with the
+** Software or, alternatively, in accordance with the terms contained in
+** a written agreement between you and The Qt Company. For licensing terms
+** and conditions see https://www.qt.io/terms-conditions. For further
+** information use the contact form at https://www.qt.io/contact-us.
+**
+** GNU Free Documentation License Usage
+** Alternatively, this file may be used under the terms of the GNU Free
+** Documentation License version 1.3 as published by the Free Software
+** Foundation and appearing in the file included in the packaging of
+** this file. Please review the following information to ensure
+** the GNU Free Documentation License version 1.3 requirements
+** will be met: https://www.gnu.org/licenses/fdl-1.3.html.
+** $QT_END_LICENSE$
+**
+****************************************************************************/
+
+
+/*!
+//! [building qt for imx6quad]
+ To set up the development environment for Qt for INTEGRITY, you need to
+ build Qt from the sources for the i.MX6 Quad board. Before building Qt,
+ create a shell script that will run the exports for your environment.
+
+ \section1 Creating Script for Running Exports
+
+ Create a new shell script \e{setEnvironment.sh}, and save it under
+ your home folder. Add the following export commands to the script:
+
+ \badcode
+ export PATH=$PATH:/usr/ghs/comp_201654
+ export INTEGRITY_DIR=/usr/ghs/int1144
+ export INTEGRITY_BSP=platform-cortex-a9
+ export GL_INC_DIR=/usr/ghs/int1144/INTEGRITY-include/Vivante/sdk/inc
+ export GL_LIB_DIR=/usr/ghs/int1144/libs/Vivante
+ \endcode
+
+ These exports assume you have used the default installation directories
+ while installing MULTI IDE and INTEGRITY (see
+ \l {Installing Platform Dependencies}). If you have not used the default
+ directories, you need to adjust the exported paths accordingly.
+
+ To initialize your build environment, run the following command in a terminal:
+
+ \badcode
+ source ~/setEnvironment.sh
+ \endcode
+
+ \note You need to run this command in your terminal every time you build Qt,
+ or use the \c qmake build system.
+
+ \section1 Getting Qt Source Code
+
+ You can download the Qt source code via your
+ \l {https://login.qt.io/login} {Qt Account}.
+
+ You can also get the Qt sources via the Git version control system. Qt Wiki has
+ instructions for getting Qt sources via Git, see
+ \l {https://wiki.qt.io/Building_Qt_5_from_Git#Getting_the_source_code}.
+ You find the step by step instructions also from \l {Getting Qt Sources via Git}.
+
+ \section2 Getting Qt Sources via Git
+
+ Clone the top-level Qt 5 repository by running the following command in
+ a terminal:
+
+ \badcode
+ git clone git://code.qt.io/qt/qt5.git
+ \endcode
+
+ \note If you are behind a firewall and want to use the HTTPS protocol,
+ you can clone the top-level Qt 5 repository with the following command:
+
+ \badcode
+ git clone https://code.qt.io/qt/qt5.git
+ \endcode
+
+ Check out the target branch and the Qt sources with the following commands:
+
+ \badcode
+ cd qt5
+ git checkout <Qt version>
+ perl init-repository
+ \endcode
+
+ For example, the \c {git checkout} command for Qt 5.9.0 is \c {git checkout 5.9.0}.
+
+ The init-repository script initializes the Qt 5 repository and clones various
+ Qt 5 sub-modules (see
+ \l {https://wiki.qt.io/Building_Qt_5_from_Git#Getting_the_submodule_source_code}).
+ Qt modules supported by Qt for INTEGRITY are listed in \l {Supported Qt Modules}.
+
+ \section1 Configuring Qt
+
+ Configure Qt for the i.MX6 Quad board with the following command:
+
+ \badcode
+ cd <Qt installation directory>
+ ./configure -developer-build -xplatform integrity-armv7-imx6 -confirm-license
+ -opensource -nomake examples -nomake tests -no-dbus -silent -opengl es2 -static
+ \endcode
+
+ \note INTEGRITY supports only static Qt builds.
+
+ \section1 Building Qt
+
+ Build Qt with the \c make command in the terminal. You can run \c make with as
+ many cores on your host machine as you desire. In our example we use six cores:
+
+ \badcode
+ make -j6
+ \endcode
+
+ \section1 Installing Qt
+
+ If you have not used the configure options
+ \c {-developer-build} or \c {-prefix $PWD/qtbase} in \l {Configuring Qt},
+ run the following command in a terminal:
+
+ \badcode
+ cd <Qt installation directory>
+ make install
+ \endcode
+
+ If you have used the configure options \c {-developer-build} or
+ \c {-prefix $PWD/qtbase}, you can use Qt from the build
+ directory, without running the \c {make install} command.
+
+ Qt is now configured and built for the i.MX6 Quad board.
+//! [building qt for imx6quad]
+*/
diff --git a/doc/src/platforms/platform-notes-integrity.qdoc b/doc/src/platforms/platform-notes-integrity.qdoc
new file mode 100644
index 0000000000000000000000000000000000000000..0432f683d85041fd6615afca583ae1faf773ab6d
--- /dev/null
+++ b/doc/src/platforms/platform-notes-integrity.qdoc
@@ -0,0 +1,78 @@
+/****************************************************************************
+**
+** Copyright (C) 2017 The Qt Company Ltd.
+** Contact: https://www.qt.io/licensing/
+**
+** This file is part of the documentation of the Qt Toolkit.
+**
+** $QT_BEGIN_LICENSE:FDL$
+** Commercial License Usage
+** Licensees holding valid commercial Qt licenses may use this file in
+** accordance with the commercial license agreement provided with the
+** Software or, alternatively, in accordance with the terms contained in
+** a written agreement between you and The Qt Company. For licensing terms
+** and conditions see https://www.qt.io/terms-conditions. For further
+** information use the contact form at https://www.qt.io/contact-us.
+**
+** GNU Free Documentation License Usage
+** Alternatively, this file may be used under the terms of the GNU Free
+** Documentation License version 1.3 as published by the Free Software
+** Foundation and appearing in the file included in the packaging of
+** this file. Please review the following information to ensure
+** the GNU Free Documentation License version 1.3 requirements
+** will be met: https://www.gnu.org/licenses/fdl-1.3.html.
+** $QT_END_LICENSE$
+**
+****************************************************************************/
+
+
+/*!
+ \page platform-notes-integrity.html
+ \title Platform Notes - INTEGRITY
+ \contentspage Platform Notes
+ \keyword INTEGRITY
+
+ From Qt 5.9 onwards, the Green Hills Software
+ \l {http://www.ghs.com/products/rtos/integrity.html} {INTEGRITY}
+ Real-Time Operating System (RTOS) is a supported platform.
+
+ The INTEGRITY RTOS is widely used in safety- and security-critical systems.
+ Especially in the automotive industry, both Qt and the INTEGRITY RTOS can be
+ used in conjunction with instrument clusters and infotainment systems.
+
+ With Qt for INTEGRITY you can build and develop applications for the
+ INTEGRITY RTOS. Qt for INTEGRITY supports most \l {Supported Qt Modules} {Qt Modules}.
+ The development environment includes your target device and Qt sources
+ that you need to build for your target device.
+ See \l {Supported Development Hosts and Boards} for detailed information
+ about the supported development environment.
+
+ Qt for INTEGRITY has a tutorial that helps you learn how to:
+ \list
+ \li Set up a development environment for the i.MX6 Quad board
+ \li Build an INTEGRITY application
+ \li Prepare the i.MX6 Quad board to run your application
+ \endlist
+
+ See \l {Qt for INTEGRITY: Monolith Project Tutorial}.
+
+ \section1 Supported Qt Modules
+
+ Qt for INTEGRITY has been tested to support the following Qt modules: Qt Core,
+ Qt Network, Qt GUI, Qt Quick, Qt QML, Qt Quick Controls 2, Qt 3D, Qt Widgets,
+ Qt Image Formats, Qt XML Patterns, Qt SVG.
+
+ Other Qt modules may work with Qt for INTEGRITY, but we cannot guarantee that.
+
+ \section1 Supported Development Hosts and Boards
+
+ Qt for INTEGRITY can be built on 64-bit Linux distributions.
+
+ Qt for INTEGRITY supports building and developing applications for the
+ following development boards:
+ \list
+ \li \l {https://boundarydevices.com/product/sabre-lite-imx6-sbc/}
+ {Boundary Devices BD-SL-i.MX6}
+ \li \l {http://www.nvidia.com/object/tegra-x1-processor.html} {NVIDIA Tegra X1}
+ \endlist
+*/
diff --git a/doc/src/platforms/platform-notes-rtos.qdoc b/doc/src/platforms/platform-notes-rtos.qdoc
index c1ef19f8cfc9aa42ebd2e2048f866a7022e75d0f..2ca9d651a01d9e42c25242cfab0941ea78ce650d 100644
--- a/doc/src/platforms/platform-notes-rtos.qdoc
+++ b/doc/src/platforms/platform-notes-rtos.qdoc
@@ -326,15 +326,3 @@
\l{Installing Files} in the \l {QMake} documentation for more details.
*/
-
-/*!
- \page platform-notes-integrity.html
- \title Platform Notes - INTEGRITY
- \contentspage Platform Notes
- \keyword INTEGRITY
-
- \note \l {http://www.ghs.com/products/rtos/integrity.html}{INTEGRITY} is a community supported platform
-
- \sa {http://blog.qt.io/blog/2012/06/01/developing-with-qt-commercial-for-integrity-on-windows-a-step-by-step-guide-to-configure-and-compile-qt-commercial-on-integrity-2/}{Developing with Qt Commercial for INTEGRITY on Windows}
- \sa {http://qt.gitorious.org/qt/qt-integrity}{the git repository}
-*/
diff --git a/doc/src/platforms/supported-platforms.qdocinc b/doc/src/platforms/supported-platforms.qdocinc
index d9e23c22bedd11a2a488495503ca0ef9d07279a8..83947b6e8d2645e38be0ba136d8dae0d2433ab4e 100644
--- a/doc/src/platforms/supported-platforms.qdocinc
+++ b/doc/src/platforms/supported-platforms.qdocinc
@@ -89,13 +89,16 @@ Mobile Platforms: \l {Qt for Android}{Android},
\li
\row \li {3,1} \header \li {3,1}
- Embedded Platforms: \l {Qt for Embedded Linux}{Embedded Linux}, \l {QNX}
+ Embedded Platforms: \l {Qt for Embedded Linux}{Embedded Linux}, \l {QNX}, \l {INTEGRITY}
\row \li \l {Qt for Embedded Linux}{Embedded Linux}
\li GCC \li ARM Cortex-A, Intel boards with GCC-based toolchains
\row \li QNX 6.6.0, 7.0 (armv7le and x86)
\li \b {GCC as provided by QNX}
\li Hosts: \b {RHEL 6.6 (64-bit)}, \b {RHEL 7.2 (64-bit)},
\b {Windows 10 (64-bit)}, \b {Windows 7 (32-bit)}
+ \row \li \l {INTEGRITY} {INTEGRITY 11.4.x}
+ \li As provided by Green Hills INTEGRITY
+ \li Hosts: 64-bit Linux
\row \li {3,1} \header \li {3,1}
Mobile Platforms: \l {Qt for Android}{Android}, \l {Qt for iOS}{iOS},