Have you run your program under the debugger and looked at the traceback when whatever you mean by "app crash" occurs? Are you under Linux with core dumps? That is always by far the best place to start from.
If no core dumps and you can't run under debugger (e.g. it runs unattended overnight), what about putting in extensive but basic logging lines (to file) to see where it's going?
@SGaist Thanks for your help. I'm trying to use the same library across platforms. I found a way to compile the openldap library for mac/iOS version using this link https://www.ibm.com/developerworks/aix/library/au-iphoneapp/?ca=drs- . In the same way I'm trying to find the ways for compiling the library with MSVC and GCC so that the code for connecting, authentication and queries will be same on all the platforms. I know this is out Qt scope but trying to find whether someone succeeded in doing it.
It depends on your OS. Since you use the MSVC compiler I guess I can assume its windows.
In that case you can add an environment variable from the System/Advanced System Settings/Environment Variables.
I'd check the docs for the camera's SDK. There may be other things that need to be set.
Does the Windows camera app connect to it ?
@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:
had it instead been *wektor=SafeArrayCreate(VT_VARIANT,1,&granice); then a QList<QVariant> should've worked.
Qt's COM support is kind of stuck between a rock (everything is a VARIANT, the Visual Basic COM flavor, functions are called 100% through the IDispatch interface) and a hard place (you can pass native data types like int, doubles etc through COM, the C/C++ COM flavor, functions are called through specialized interfaces based on IUnknown). I remember doing a lot COM coding around the turn of the century, it was really hot then. Nowadays not so much :-)
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.
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.
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.