On Mon, Nov 24, 2008 at 2:45 PM, Tyler Roscoe <span dir="ltr"><<a href="mailto:tyler@cryptio.net">tyler@cryptio.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, Nov 24, 2008 at 02:22:22PM -0500, <a href="mailto:David.Karr@L-3COM.COM">David.Karr@L-3COM.COM</a> wrote:<br>
> In a certain project where we started using CMake about five years ago,<br>
> it used to be that when we opened the Visual Studio 6.0 workspace<br>
> created by CMake, the ALL_BUILD project was conveniently defined as the<br>
> "startup project" already, meaning that all one had to do was to click<br>
> the "Build" button (or press F7) to build the entire workspace. (OK,<br>
</div>[snip]<br>
<div class="Ih2E3d">> So, the question: Does anyone want this?<br>
<br>
</div>I think this is a good idea. Our developers are also accustomed to this<br>
behavior, so if CMake can do the same thing with the sln/vcproj files it<br>
generates, that will be one less workflow change for them to deal with.</blockquote><div><br>Yes, please post the patch and/or open a bug entry and attach it. This has been an annoying thorn in the sides of our windows developers for what seems like forever.<br>
<br></div></div>-- <br>Philip Lowman<br>