Re: [cmake-developers] Visual Studio Project Upgrade Prompt

2016-11-04 Thread Brad King
On 11/03/2016 06:05 PM, Christensen, Erik wrote:
> VS_GLOBAL_VCProjectUpgraderObjectName NoUpgrade
[snip]
> Really, it seems like this is a property that should be applied by
> default to any CMake generated Visual Studio projects.

Yes.  Please look at cmVisualStudio10TargetGenerator.cxx to try that.

Thanks,
-Brad

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers


[cmake-developers] Visual Studio Project Upgrade Prompt

2016-11-03 Thread Christensen, Erik
Hi,

When opening projects in the Visual Studio IDE that are using an older toolset 
version (ie. a VS 2012 project under VS 2015) for the first time, a prompt is 
displayed asking if you'd like to upgrade the projects to the newer version of 
Visual Studio.  This gets annoying pretty quickly when you're generating 
projects over and over.  Now, there's a VS project property that can be set, 
which will prevent this prompt from being shown.  It can be applied to any 
(known) CMake target like so:

set_property(TARGET target PROPERTY VS_GLOBAL_VCProjectUpgraderObjectName 
NoUpgrade)

Unfortunately, you still get upgrade prompts for all of the predefined and 
automoc targets (ie. ALL_BUILD, ZERO_CHECK, etc.).  Is there any way to assign 
that property to the built-in targets?

Really, it seems like this is a property that should be applied by default to 
any CMake generated Visual Studio projects.   I'm not sure why anyone would 
want to do a project upgrade within Visual Studio itself when you can just 
reconfigure the toolset in CMake.  I imagine anyone specifying an older toolset 
version is doing so on purpose so that they can use the latest IDE with 
projects that need to be kept on older compilers.  But maybe I'm wrong.

Erik
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers