Re: [CMake] Visual Studio reload projects
We have created a Visual Studio macro that will reload the .sln solution file in order to avoid clicking Reload in multiple dialogs. It currently works with Visual Studio 8 2005 (and probably with VS 9 2008, also, but not yet tested in that environment.) The macro is called automatically by CMake only when necessary and will prompt the developer only when a .sln file or .vcproj file has changed. Try out the nightly Windows CMake installer found here to see if it solves the problem for you: http://www.cmake.org/files/vCVS/cmake-2.5.20071126-win32-x86.exe Please reply here to the CMake mailing list with additional comments or problem reports. Thanks, David Cole Kitware, Inc. On 8/28/07, KSpam [EMAIL PROTECTED] wrote: One major annoyance that users have with CMake integration in VisualStudio is having to click Yes to reload the project files after CMake regenerates them. There is no Yes to All option. With hundreds of projects, it takes a while to click all of the Yes buttons. Does anyone know if there is a way to force the reload in Visual Studio, so that the user is not bothered with the dialog boxes? Is there a configuration option in Visual Studio? I tell the users to exit Visual Studio, reconfigure CMake, and then reopen Visual Studio, but that is a suboptimal solution. Thanks, Justin ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio reload projects
Torsten Martinsen wrote: gga wrote: KSpam wrote: I agree that this is a Visual Studio issue; however, I am wondering if anyone knows a workaround. I am not a Windows developer, but I figured that someone on this list would have found a reasonable solution. Sure. Don't use Visual Studio. Stick to nmake and a good editor like emacs. You'll be a happier person in the long run. I, too, use Emacs. However, do not be oblivious to the fact that an nmake build can take around five times longer than an IDE build. Performance is one reason, yes -- especially in these multicore times; nmake cannot handle parallell builds -- but the most (or only) compelling reason to use Visual Studio as opposed to Emacs + command line builds is that the Visual Studio debugger is superior to all other debuggers available on Windows. -- /Jesper ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio reload projects
Jesper Eskilson wrote: I, too, use Emacs. However, do not be oblivious to the fact that an nmake build can take around five times longer than an IDE build. Performance is one reason, yes -- especially in these multicore times; nmake cannot handle parallell builds -- but the most (or only) compelling reason to use Visual Studio as opposed to Emacs + command line builds is that the Visual Studio debugger is superior to all other debuggers available on Windows. I use gmake with the Unix Makefile generator and cl as the compiler. gmake does have parallel builds. I use the patched cygwin gmake from here: http://*www.cmake.org/files/cygwin/make.exe -Bill * ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Visual Studio reload projects
Manuel Klimek wrote: On 8/30/07, Torsten Martinsen [EMAIL PROTECTED] wrote: I, too, use Emacs. However, do not be oblivious to the fact that an nmake build can take around five times longer than an IDE build. why do you use nmake and not msbuild if you do a command line build? msbuild uses the same mechanism the IDE uses, but without the IDE (it's a command line tool). It's basically an xml based make-replacement, and you can easily open your projects in the IDE if you need to, for example for debugging... Pardon me if I am wrong, but AFAICT MSBuild uses its own project file format, and not .vcproj files. This would make it pretty hard to use with CMake... Are you perhaps thinking of vcbuild? -Torsten ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
RE: [CMake] Visual Studio reload projects
gga wrote: KSpam wrote: I agree that this is a Visual Studio issue; however, I am wondering if anyone knows a workaround. I am not a Windows developer, but I figured that someone on this list would have found a reasonable solution. Sure. Don't use Visual Studio. Stick to nmake and a good editor like emacs. You'll be a happier person in the long run. I, too, use Emacs. However, do not be oblivious to the fact that an nmake build can take around five times longer than an IDE build. -Torsten This e-mail and any files sent with it contain information that may be privileged or confidential and is the property of the GateHouse Group. This information is intended solely for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use the message or any part thereof. If you have received this e-mail in error, please notify the sender immediately, and delete all copies of this message. In accordance with GateHouse Security Policy, e-mails sent or received may be monitored. ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio reload projects
I do not have Visual Studio around, but found that on the net: After saving a file, the add-in kicks in and start replacing carriage returns and line feeds. If the file is opened in Visual Studio, it will open a dialog box saying that the file has changed, and will ask if you want to reload it. This is quite annoying so you can set up Visual Studio to automatically reload changed files. To do this, select: Tools | Options | Editor, and check Automatic reload of externally modified files. http://www.codeproject.com/macro/stripem.asp Is this working for you ? HTH -Mathieu On 8/29/07, KSpam [EMAIL PROTECTED] wrote: I agree that this is a Visual Studio issue; however, I am wondering if anyone knows a workaround. I am not a Windows developer, but I figured that someone on this list would have found a reasonable solution. On Tuesday 28 August 2007 16:18:34 Andrew Maclean wrote: From memory, I am pretty sure that this is a Visual Studio issue. I agree that it is a pain but I think the solution outlined below is the only one. On 8/29/07, KSpam [EMAIL PROTECTED] wrote: One major annoyance that users have with CMake integration in VisualStudio is having to click Yes to reload the project files after CMake regenerates them. There is no Yes to All option. With hundreds of projects, it takes a while to click all of the Yes buttons. Does anyone know if there is a way to force the reload in Visual Studio, so that the user is not bothered with the dialog boxes? Is there a configuration option in Visual Studio? I tell the users to exit Visual Studio, reconfigure CMake, and then reopen Visual Studio, but that is a suboptimal solution. Thanks, Justin ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake -- Mathieu ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
Re: [CMake] Visual Studio reload projects
On 8/30/07, Torsten Martinsen [EMAIL PROTECTED] wrote: I, too, use Emacs. However, do not be oblivious to the fact that an nmake build can take around five times longer than an IDE build. why do you use nmake and not msbuild if you do a command line build? msbuild uses the same mechanism the IDE uses, but without the IDE (it's a command line tool). It's basically an xml based make-replacement, and you can easily open your projects in the IDE if you need to, for example for debugging... Manuel -- http://klimek.box4.net ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
[CMake] Visual Studio reload projects
One major annoyance that users have with CMake integration in VisualStudio is having to click Yes to reload the project files after CMake regenerates them. There is no Yes to All option. With hundreds of projects, it takes a while to click all of the Yes buttons. Does anyone know if there is a way to force the reload in Visual Studio, so that the user is not bothered with the dialog boxes? Is there a configuration option in Visual Studio? I tell the users to exit Visual Studio, reconfigure CMake, and then reopen Visual Studio, but that is a suboptimal solution. Thanks, Justin ___ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
