Please allow control of VS generator for WinCE project/target deploy setting
Currently, all EXE and shared library projects for WindowsCE are tagged by CMake to deploy (when choosing Deploy Solution) in the generated VS10+ solution file. A line such as:
{9F7C86D8-1ED2-3B69-8B28-A9691E0B9E6A}.Release|STARDARD_SDK_500.Deploy.0 = Release|STARDARD_SDK_500
containing 'Deploy' appears in the .sln file.
There are a couple of reasons to want to control this more finely in use cases with large numbers of build targets:
- VS supports setting a different target IP deployment address for each target/project. For a solution with many projects, having to set or change the deployment IP address for each project is tedious.
- VS will already automatically deploy build dependencies of any deployed EXE or shared library, even if not set to deploy in the solution configuration. The target IP address used for all the dependencies is the one for the exe / shared lib, in other words, it only needs to be set once in the IDE.
- A solution might have multiple EXEs and various shared libraries, not all of which are required in each deploy/debugging scenario. Deploying all of them to the target may take too much time or there might not be sufficient memory to receive all of the binaries. It is nice to be able to use 'deploy solution' to deploy a commonly used or 'primary' EXE and dependent libraries - which could be configured with CMake.
A suggestion might be to allow tagging a CMake project for non-deployment with something like:
set_property(TARGET myTarget PROPERTY VS_NO_SOLUTION_DEPLOY TRUE)
This would tag target 'myTarget' to NOT be marked for deployment in the generated VS solution configuration.