On 9/10/2012 5:38 PM, J Decker wrote:
I will probably complain from now until it's fixed with a perference
(which will probably mean me writing a patch; but... )
Devenv has a side effect that msbuild does not; devenv writes to the
most recently used projects, msbuild does not. So I can keep us
I will probably complain from now until it's fixed with a perference
(which will probably mean me writing a patch; but... )
Devenv has a side effect that msbuild does not; devenv writes to the
most recently used projects, msbuild does not. So I can keep using
visual studio to build my other c# p
I woudl rather have it discover it for the appropriate version of
visual studio I select as a generator, I have already copied the
findprogram code from the script and put it at the head of a couple of
the scripts, but this doesn't fix that the outer layer is still being
built with devenv. I don't
On Fri, Jun 8, 2012 at 6:26 PM, Óscar Fuentes wrote:
> J Decker writes:
>
>> I mean using cmake --build . and/or getting BUILD_COMMAND from cmake
>> which comes back as devenv which is then used to build projects.
>>
>> I had a bunch of cmake projects that built from a batch file, then I
>> made
J Decker writes:
> I mean using cmake --build . and/or getting BUILD_COMMAND from cmake
> which comes back as devenv which is then used to build projects.
>
> I had a bunch of cmake projects that built from a batch file, then I
> made a cmakelists that does the same thing, so I have one
> cmakeli
I mean using cmake --build . and/or getting BUILD_COMMAND from cmake
which comes back as devenv which is then used to build projects.
I had a bunch of cmake projects that built from a batch file, then I
made a cmakelists that does the same thing, so I have one
cmakelists.txt which builds all other
Hi,
Sorry but it's not clear to me: when you say "using devenv" do you
mean opening the IDE, or do you mean calling devenv form the
command-line like "devenv /build Debug mysolution.sln"? The former is
slow due to IntelliSense, ReSharper, etc but the latter is very fast.
On Fri, Jun 8, 2012 at 5
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
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 fo
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 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 th
On 6/1/2012 6:49 PM, J Decker 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
11 matches
Mail list logo
