CMake, MSVS and Qt: Advice needed on development, testing and deployment ools

Please see the picture below for the dll dependencies in my apps.
1. gApps & gDlls refer to 1 or more GUI apps and modules.
2. bApps, bDlls & bDlls(c) refer to backend computational apps and modules.
3. Note that common bDlls(c) are used in building and deploying gApps as well.

Primary goal is to be cross-platform compatible for build/testing/development and application deployment aspects (Windows and Linux for the foreseeable future). The chosen tools should support incremental builds and testing as part of the build.

What's been chosen so far (I won't go into the reasons):
1. For all of b modules and apps (purple dashed box) MSVS, CMake & CTest.
2. For all of g modules and apps Qt will be the platform, that too on Windows.

Need experts' advice and opinion on the rest:
1. Go native Qt development or MSVS Qt Add-in? Assume that no Qt convenience, say extensible Qt plug-ins, can be sacrificed.
2. If Qt is the chosen platform, what build system (qmake or CMake) is more practical? If MSVS Qt Add-in is the platform, then what should be the choice for build tools?
3. What about setting up and packaging of bDlls(c) to be consumed by g modules. Also how easy or difficult is to automate the dependencies of g modules on bDlls(c)?

I am also willing to live with certain level of human intervention: for example, if g dependencies on bDlls(c) cannot be entirely automated (say testing is not, but building part is automated), I am ok with it. Or is there a holy grail that satisfies my needs. Thank you very much for all your advice.