Well, I seem to have solved it. The error I was getting wasn't particularly helpful. In reality, I needed to also include the aws-sdk-core library in addition to the aws-sdk-sqs. It is now happily building and sending messages to SQS. I did still use the brew version of the aws-sdk-cpp. I'll have to work on getting the cmake to build the sdk-build directory the way QT wants. Yet another new thing to wrap my head around. But this gives me something to wire up with other projects via messaging so I'm excited to keep going now.
Thank you. Directly over QFile :: wirite as ByteArray works without problems. Now all I have to do is find out how to check the password. But for this I make another thread on as soon as I can deal with it.
I have fixed the problem - I'm now implementing the tools that I have wanted to implement without any long lasting errors. I just started a new project over and doing that led me to solve my problems (along with your techniques & guidance) though I would like to leave it out of this context here in the forum.
Thank you for your time and patience.
It usually depends on how the library itself works. You can queue "commands" you want the library to execute and your thread can execute them one after the other, or you can use QtConcurrent which is higher level thread management.
@jalal_ba you're using OpenCV 3.4 and the guide you referred is using OpenCV 3.2 could it be possible you try with the old version to see what happens?
In addition, the error you have is related to Google protobuf, so you may want to check this issue regarding OpenCV and protobuf under Windows.
To achieve a single executable that "just runs" on Windows you usually statically link your app and add any needed resources (images, scripts etc.) using the resource system. No special app is needed for that.
That's the standard way to do it. It's the easiest, the fastest and makes least problems to the user.
If you can't do that for any reason you can also create a self extracting archive using one of the popular packers, e.g. 7zip (example here).
When the user specifies his password, hash it and stored the hashed to the database.
When a user tries to logon and specifies a proposed password, hash that and pass it to query like you have to see if it is same as a hash in the database row.
So you never pass the unhashed/clear text of the password to/from the database.
Disabled Categories are greyed out
This topic will be moved to the category
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.