[cmake-developers] visual studio usage

J Decker d3ck0r at gmail.com
Fri Jun 8 11:59:06 EDT 2012


There are two reasons this is an issue (for me)

1) using devenv to build is MUCH slower on many of the projects than
just using MSBuild.  ... yes I know, longer build times mean more time
at the water cooler or whatever...

2) Using devenv, each project that gets built becomes a
most-recently-used file for visual studio, so the things I'm actually
working on (not the dozens of projects that get built with automated
method) get lost; they get shoved off the list of recently used files
pretty quick.

On Thu, Jun 7, 2012 at 9:22 AM, J Decker <d3ck0r at gmail.com> wrote:
> Okay I saw the comments in the platform scripts about fortran, but
> maybe a symbol could be added to maybe prefer msbuild; there are a
> couple like that for InstallSystemRuntimeLibraries or whatever that
> was... so you can control the behavior.  The other alternative might
> be add additional options for generators that prefer one or the other.
>
> if( PREFER_MSBUILD )
>
> On Sat, Jun 2, 2012 at 2:17 PM, Pau Garcia i Quiles
> <pgquiles at elpauer.org> wrote:
>> Hi,
>>
>> It will probably introduce other problems:
>>
>> MsBuild woes
>> http://www.elpauer.org/?p=955
>>
>>
>> On Sat, Jun 2, 2012 at 12:49 AM, J Decker <d3ck0r at gmail.com> wrote:
>>> shouldn't cmake use 'msbuild' instead of 'devenv.com' or 'devenv.exe'?
>>>
>>> I have a feeling that would solve one of my issues with visual studio,
>>> in that after building a long chain of cmake projects using visual
>>> studio, all of the most recent project references are updated to being
>>> the projects that were built, thereby losing the projects I'm actually
>>> working on.
>>
>> --
>> Pau Garcia i Quiles
>> http://www.elpauer.org
>> (Due to my workload, I may need 10 days to answer)



More information about the cmake-developers mailing list