Important: Please read the Qt Code of Conduct -

StaticLib deployed as executable on Android Kit deployment

  • Hi,

    So there's a small issue that I've worked around for some time now, that I'd finally would like to get to the bottom of. I have 2 projects, where one of them acts as a static library for the other executable project. Lets call them SharedLib and Game.

    Game depends on SharedLib, and whenever I recompile Game and SharedLib is out of date, it gets compiled as well (naturally). This works as expected for desktop builds. When I switch to an Android Kit (for both), Qt Creator (for lack of better term) launches 2 "select your Android device to deplay to" screens, instead of just one. It does not seem to realize that SharedLib is just a static library and will not have its own executable.

    My workaround for this has been to just uncheck the dependency setting that Game needs SharedLib in the project settings and just build SharedLib manually before deploying Game. Once I got back to a Desktop kit, I just remember to recheck the dependency.

    This happens in 5.1, 5.2 and 5.3 on Linux and Windows 7 (though the project settings has not changed much)
    As you can see, it's not a big issue, and i'm sure it's just a small configuration error on my part. Any ideas?

Log in to reply