One might be able to use FILE() to generate a .vcxproj.user if( NOT EXISTS )
This is a version from 2012 project. ALL_BUILD.vcxproj.user (it's the default project. so it's the one i usually set, unless something clever along these lines happened.... ) <?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" xmlns=" http://schemas.microsoft.com/developer/msbuild/2003";> <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"> <LocalDebuggerCommand>C:\General\Build\karaway\chatment\output\bin\chatment.exe</LocalDebuggerCommand> <LocalDebuggerWorkingDirectory>C:\General\Build\karaway\chatment\output\bin</LocalDebuggerWorkingDirectory> <DebuggerFlavor>WindowsLocalDebugger</DebuggerFlavor> </PropertyGroup> </Project> ------------- That's not even a very large file to write the whole thing.... Another for VS14 <?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" xmlns=" http://schemas.microsoft.com/developer/msbuild/2003";> <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'"> <LocalDebuggerCommand>C:\General\Build\sack-x64\Debug_out\core\bin\test.json.parser.exe</LocalDebuggerCommand> <LocalDebuggerCommandArguments> </LocalDebuggerCommandArguments> <LocalDebuggerWorkingDirectory>C:\General\Build\sack-x64\Debug_out\core\bin</LocalDebuggerWorkingDirectory> <DebuggerFlavor>WindowsLocalDebugger</DebuggerFlavor> </PropertyGroup> </Project> ----------- I guess there's some platform settings that will make it bigger, but done in a foreach( target ) writeProjectUser( target ) shouldn't be too painful... On Mon, Jun 20, 2016 at 2:11 PM, Stephen Kelly <steve...@gmail.com> wrote: > J Decker wrote: > > > The setting is in a different file that's .vcproj.user (or .user.vcproj) > > And there is not one of these for each project() command? > > It seems to me that this should either be a GLOBAL property, or the > documentation which directory to set the DIRECTORY property on. I have no > idea what the answer is. > > Thanks, > > Steve. > > > -- > > 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 >
-- 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
