Hi,
This makes cmake --build much less predictable across cmake versions and cmake
projects.
How can I find out if msbuild is chosen without inspecting the cmake project?
Specifying this manually is not really an option... too complicated.
Or like that:
- run CMake
- get the CMAKE_VS_MSBUILD...
Ok, so it all seems to boil down to the following:
- 2.8.12: cmake --build uses devenv to build, which in turn picks
up a setting (maximum number of parallel project builds) from the VS
IDE at build time. As this was set to 8 on my machine, by default the
build used parallellization with 8 cores
On 01/20/2015 03:40 PM, Paul Smith wrote:
Where can I go to find out more about how cmake --build chooses whether
to use msbuild vs. devenv?
The behavior was updated in 3.0 and is now described here:
http://www.cmake.org/cmake/help/v3.0/variable/CMAKE_MAKE_PROGRAM.html
In 2.8.12 and below we
3.1.0:10m50s
2.8.12: 4m02s
3.1.0 (/MP): 6m29s
2.8.12 (/MP): 3m48s
I cannot reproduce that. On my machine for OpenCV (as of commit
5e92a777) I get about the same time for either version of CMake.
3.1.0 : 8m57s
2.8.12.2 : 8m58s
3.1.0(/MP): 4m52s
2.8.12.2
If you open the Tools Options dialog in Visual Studio, and
navigate to the Projects and Solutions Build and Run tab, what is
your maximum number of parallel project builds value?
For maximum parallel build capability, it should be set to the same as
the number of cores you have.
D
On Tue,
On 01/20/2015 07:10 AM, Yves Frederix wrote:
msbuild ALL_BUILD.vcxproj /p:Configuration=Release
/p:VisualStudioVersion=12.0
(shouldn't this have been VisualStudioVersion=11.0?)
Yes, but I was testing with VS 2013.
When keeping an eye on the resource monitor, I can also see that,
while
If you open the Tools Options dialog in Visual Studio, and
navigate to the Projects and Solutions Build and Run tab, what is
your maximum number of parallel project builds value?
This is set to 8, which is what I expect as I have 4 cores with
hyperthreading (also to windows they show as 8
Hi,
but msbuild does not use this setting from VS, only devenv does.
See option /m
HS
Am 20. Januar 2015 14:54:26 MEZ, schrieb David Cole via CMake cmake@cmake.org:
If you open the Tools Options dialog in Visual Studio, and
navigate to the Projects and Solutions Build and Run tab, what is
On Tue, 2015-01-20 at 16:02 -0500, Paul Smith wrote:
I think devenv is used instead of msbuild when the solution has
fortran projects.
I certainly don't have any Fortran projects--!!
I think I figured it out: on our build servers we don't delete
everything and start over from scratch all
On 20.01.2015 21:40, Paul Smith wrote:
Where can I go to find out more about how cmake --build chooses whether
to use msbuild vs. devenv? It has to be something more complicated than
just the generator used, otherwise all of these systems would use
msbuild.
I think devenv is used instead of
On Tue, 2015-01-20 at 21:57 +0100, Nils Gladitz wrote:
On 20.01.2015 21:40, Paul Smith wrote:
Where can I go to find out more about how cmake --build chooses whether
to use msbuild vs. devenv? It has to be something more complicated than
just the generator used, otherwise all of these
Am 20. Januar 2015 14:54:26 MEZ, schrieb David Cole via CMake
cmake@cmake.org:
If you open the Tools Options dialog in Visual Studio, and
navigate to the Projects and Solutions Build and Run tab, what is
your maximum number of parallel project builds value?
For maximum parallel build
On 01/17/2015 12:20 PM, Yves Frederix wrote:
I also tested with the build of an 'open' project (the crypto example
was part of a work-related project). The results below are for the
compilation of OpenCV (latest git from
https://github.com/itseez/opencv), again with VS2012 Win64, Release
only
Hi,
I also tested with the build of an 'open' project (the crypto example
was part of a work-related project). The results below are for the
compilation of OpenCV (latest git from
https://github.com/itseez/opencv), again with VS2012 Win64, Release
only and no tweaking of the CMake settings.
snip
Are you building the same configuration in both cases?
Use
cmake --build . --config Debug
or
cmake --build . --config Release
Yes, I used --config Release in both cases.
to specify the configuration. You could also compare the .vcxproj
files that are generated.
I had a look
On 01/16/2015 05:24 AM, Yves Frederix wrote:
3.1.0:
ALL Crypto Crypto_sCrypto_test
real0m38.211s 0m14.023s 0m7.003s0m14.691s
2.8.12:
ALL Crypto Crypto_sCrypto_test
real
Hi,
3.1.0:
ALL Crypto Crypto_sCrypto_test
real0m38.211s 0m14.023s 0m7.003s0m14.691s
2.8.12:
ALL Crypto Crypto_sCrypto_test
real0m27.230s 0m17.110s 0m10.231s
On 01/15/2015 11:47 AM, Yves Frederix wrote:
I recently made the upgrade from v2.8.12 to v3.1.0. Unfortunately, I
am now experiencing a serious decrease in build speed for the VS2012
Win64 builds.
[snip]
gives the impression that the difference might be due to a change in
default compilation
Hi all,
I recently made the upgrade from v2.8.12 to v3.1.0. Unfortunately, I
am now experiencing a serious decrease in build speed for the VS2012
Win64 builds. I have searched the cmake mailings but I was unable to
find a reference to a similar issue.
To give an idea about the difference I am
19 matches
Mail list logo
