Building Qt OPC UA with open62541

Qt OPC UA is not included in the Qt installer and must be built from source.
Open62541 is currently the most stable and feature complete backend, the open62541 library has minimal external dependencies and can be easily built on all supported platforms (Linux, Windows (MinGW32, MSVC 2017), Android and iOS).

Requirements

First of all, an installation of Qt 5.10 is required. Using the Qt installer also provides the necessary tools required to build Qt OPC UA.
Building open62541 requires CMake and Python. The Python package six must be installed from a terminal before starting the build by executing

Building on Linux

Build open62541

Build Qt OPC UA

Building on Windows

MinGW32

Execute the following commands in the  “Qt 5.10.0 for Desktop (MinGW 5.3.0 32 bit)” shell

Build open62541

Build Qt OPC UA

MSVC 2017

Execute the following commands in the “Qt 5.10.0 64-bit for Desktop (MSVC 2017)” shell

Build open62541

Build Qt OPC UA

Building for Android

When doing an Android build on Windows, refer to “Building on Windows” for setting the QTOPCUA_OPEN62541 environment variables and specifying the generator for CMake.

Additional requirements

An Android NDK and CMake >= 3.6.0 are required to build for Android.

Build open62541

Build Qt OPC UA

Building for iOS

Additional requirements

XCode is required to build for iOS

Build open62541

Build Qt OPC UA

Creating the documentation

Use the same shell and the platform specific make tool that has been used in building the Qt OPC UA module. Building the docs on Linux or OS X requires using sudo to execute the second step if Qt has been installed to a location not writable by the current user.

Building the examples

Use the same shell and the platform specific make tool that has been used in building the Qt OPC UA module. The examples will be created in “examples” in the build directory.

 

2 thoughts on “Building Qt OPC UA with open62541”

    1. We are actually thinking about a server side API, but so far nothing is planed for the short to mid-term range. We currently focus on completing the client side API.

Leave a Reply

Your email address will not be published. Required fields are marked *