After we create our ‘.app’ folder and link it to all the necessary libraries (described in part 1) we are good to go for the installer and other features which will make our application look more professional.
When you have your application ready and you want to share your awesome product with the rest of the world, it is time to deploy – and the problems to begin. There are many ways to deploy an application but during the deployment process you are likely to face a lot of problems with dependencies and dynamically linked libraries.
QML provides a brand new approach to developing GUI applications for a range of different devices. This makes it really easy to write C++ apps for multiple operating systems. We can develop the same QML and QtQuick application for both desktop and mobile.
Sometimes we don’t want to allow users to run multiple instances of the app at once. We might want to do it, to prevent memory leak, files corruption or we decided there is no practical need to run two instances of our app at once. As there is many ways of completing this task, there is many tricky use cases as well where the single instance lock may fall.
I will show couple of cases how to implement this kind of secure lock and will describe advantages and disadvantages of each method.