The Open62541 plugin is built by default from the included 3rd party sources and has no external dependencies. The open62541 library uses mbedTLS for security. If the mbedTLS library is detected during configuration, security is enabled for the tests and the open62541 backend. The Open62541 source and header files bundled with Qt OPC UA have been generated from the open62541 v1.0 tag using the following commands:
cmake -DCMAKE_BUILD_TYPE=Release -DUA_ENABLE_AMALGAMATION=ON -DUA_AMALGAMATION_ARCHITECTURES="win32;posix" make
In order to disable the Open62541 plugin completely use:
qmake </path/to/qtopcua> -- -no-open62541 \encode In case you want to build a custom version of the Open62541 plugin, Open62541 v1.0 built with UA_ENABLE_AMALGAMATION=ON is required. When building at the top level, you have to specify the path to the Open62541 SDK: \code configure -system-open62541 OPEN62541_PREFIX=/path/to/sdk
If you are not building at the top level, this setting has to be given to qmake:
qmake </path/to/qtopcua> -- -system-open62541 OPEN62541_PREFIX=/path/to/sdk
If the open62541 header and library files are located in a custom path, different settings must be used:
设置 | 值 |
---|---|
OPEN62541_INCDIR | The directory which contains open62541.h |
OPEN62541_LIBDIR | The directory which contains the library file |
For example, the following settings can be used for building the open62541 plugin using a static build directly from its build directory without installing it:
OPEN62541_INCDIR=/path/to/open62541/build OPEN62541_LIBDIR=/path/to/open62541/build/bin
The output of the configuration step indicates whether the detection was successful:
Open62541 .............................. yes