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

   - qtopcua\src\3rdparty\open62541.pri
      - win32-msvc: LIBS += ws2_32.lib advapi32.lib
      - win32-g++: LIBS += -lws2_32 -ladvapi32

      - qtopcua\config.tests\mbedtls
      - 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
   mbedtls lib>\include
   - 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
   - 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 <daesde...@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
> 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@qt-project.org
> https://lists.qt-project.org/listinfo/interest
Interest mailing list

Reply via email to