[Interest] QtOpcUa Open62541 encryption
Luís Filipe Salé Borlido
luisborlido at gmail.com
Fri Nov 11 21:07:06 CET 2022
The last test I did I also had to make some changes in some files.
Some notes I have are in the following files (not sure if I added or
- win32-msvc: LIBS += ws2_32.lib advapi32.lib
- win32-g++: LIBS += -lws2_32 -ladvapi32
- LIBS += -ladvapi32
Then to compile, I usually open "x64 Native Tools Command Prompt for VS
2019" and type the following commands:
- cd <qtopcua source code>
- mkdir build
- cd build
- set PATH=%PATH%;<path to perl exe>
- set INCLUDE=%INCLUDE%;<path to openssl lib>\x64\include;<path to
- set LIB=%LIB%;<path to openssl lib>\x64\lib;<path to mbedtls lib>\lib
- C:\Qt\5.15.2\msvc2019_64\bin\qmake.exe ..
- nmake install
But I don't remember If perl is really needed and why; same for the OpenSSL
On Fri, Nov 11, 2022 at 11:12 AM Daesdemon <daesdemon at free.fr> wrote:
> Hello Qt Folks
> I am trying to compile QtOpcUa with Open62541 backend with encryption
> enabled (on Qt 5.15.2 Windows MSVC 2019 with qtcreator)
> I found that mbedtls is required.
> I compiled it without problems but i am unable to make this library
> recognized by qmake.
> How can i make qtConfig(mbedtls) to be valid to have the
> ENCRYPTION_ENABLED flag?
> And better, Is it possible to declare to qmake a custom installation
> path for the mbedtls lib ?
> For information, i have succeeded the mbedtls integration by modifying
> QtOpcUa source code, but i would like to know if there is a clean way to
> do that.
> Interest mailing list
> Interest at qt-project.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Interest