That's for the module itself. It provides the a SQLite plugin but your application won't get linked to it unless you build Qt to have that plugin builtin. Therefore, you'll have to link your application directly against the SQLite library.
AFAIK the removal of prefix "lib" is a "feature" of GCC respectively the associated linker which is the basis also for MinGW. On linux it is important to neglect and there it might be better to do on windows as well, when the project shall be used on both platforms.
However, it has its ups and downs and most of the time there are also other OS dependent settings.
I have this topic to 3rd party forum, since it referring to a library which is only Qt-based.
Beware that you might have better chances for a proper answer by addressing the question directly to the original author.
Thanks Michael. None of the variables you listed are in my environment. If they are in yours, where do they point? If you don't have them, they shouldn't be needed for cmake to be able to build the project but I'm obviously missing something .
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.