3rd Party Software

https://opencv.org/releases.html

Version 4.0.1 is available as it seems.

@jward I had rebuild this plugin today and had the same problem. I found that I had to include the GStreamer bin dir in my environment path.
I added this to my path and cmake configured correctly:
C:\gstreamer\1.0\x86\bin

Continued as https://bugreports.qt.io/browse/QTCREATORBUG-21947

@SGaist
I somehow solved the problem....
I run qmake.
Then, it manages to open the include file and run the codes, but it shows many warnings....
I don't know I must run qmake before run the codes...

While I really like the bindings themselves, the GStreamer folks have updated their Wiki page about it and wrote that they are now unmaintained. However, you have the qmlglsink that you should be able to use.

You should contact them for more information about it.

@JBonilla very nice tutorial!

Hi,

You have to add more information:

What version of Qt ? What version of iOS ? What version of QZXing ? How did you build QZxing ?

@SGaist That's good to know. thx.

We have a system with over 1000 Makefiles, many that call others to build the entire system. When the Makefile finds a dot pro file it invokes the qmake then invokes the regular make. I suppose it would be possible to write more scripts to be activated after the qmake is complete and remove said option. It would be much better to stop it at the source. It would be even better if that option were emitted only when needed. We may not be able to obtain that control but I am searching.

@ckzaner

Hi and welcome to devnet forum

For complex projects with different sub libraries the best approach is using the subdirs template.

@Mohammedbie said in Qt with OpenSSL AES 256 CBC Encryption:

EVP_EncryptUpdate

You should not use fixed size like you are doing. You should read the file you want to encrypt one block after the other. The block might be at most AES_BLOCK_SIZE but could be less because the last one will likely be smaller.

Ok, that worked and I am on my way again.
Thank you for your time and patience.

@SGaist I will do that, thanks a lot for your help

cmake not found is normal in the VS command prompt. You can use the full path to the executable to run it.