Re: [cmake-developers] Profile Cmake scripts

2016-01-05 Thread Bartosz Kosiorek
Hi Ben. 2016-01-04 17:39 GMT+01:00 Ben Boeckel : > The > big remaining problem is passing char* as an argument where functions do > std::string(arg) right away. I fixed all of those which did explicit > std::string conversions (via assignment or otherwise), but those

Re: [cmake-developers] Profile Cmake scripts

2016-01-05 Thread Ben Boeckel
On Tue, Jan 05, 2016 at 09:18:49 +0100, Bartosz Kosiorek wrote: > That's great news. > What is the branch name/link to these improvement? > Is it possible to push these improvements partially? Because the changes are so pervasive, I'd like for the branch to be bisectable, so every commit should

Re: [cmake-developers] Profile Cmake scripts

2016-01-05 Thread Daniel Pfeifer
On Tue, Jan 5, 2016 at 9:18 AM, Bartosz Kosiorek wrote: > > Hi Ben. > > 2016-01-04 17:39 GMT+01:00 Ben Boeckel : >> >> The >> big remaining problem is passing char* as an argument where functions do >> std::string(arg) right away. I fixed all of

Re: [cmake-developers] Profile Cmake scripts

2016-01-05 Thread Petr Kmoch
On Tue, Jan 5, 2016 at 1:33 PM, Daniel Pfeifer wrote: > > Generators for Xcode and Visual Studio have to generate more files. > ... and they have to process all configurations (Debug, Release, MinSizeRel, RelWithDbgInfo) during the generation stage, instead of just one

Re: [cmake-developers] Profile Cmake scripts

2016-01-04 Thread Ben Boeckel
On Sun, Dec 27, 2015 at 22:04:14 +0100, Dimitar Yordanov wrote: > I agree with you. Running valgrind directly on the cmake binary > provides useful information: I can see which internal cmake functions > are used the most and consume most of the time. > > Nevertheless, I think it would be useful

Re: [cmake-developers] Profile Cmake scripts

2015-12-27 Thread Alexander Neundorf
On Sunday, December 27, 2015 18:40:27 Dimitar Yordanov wrote: > Hi all, > > I was searching for a way to profile CMake scripts in order to find > bottlenecks and possibilities to improve performance. I found out that > someone already invested time on that [1] providing a minimal solution. The >

[cmake-developers] Profile Cmake scripts

2015-12-27 Thread Dimitar Yordanov
Hi all, I was searching for a way to profile CMake scripts in order to find bottlenecks and possibilities to improve performance. I found out that someone already invested time on that [1] providing a minimal solution. The idea behind it is to use the cmake "--trace" option and to output a time

Re: [cmake-developers] Profile Cmake scripts

2015-12-27 Thread Dimitar Yordanov
2015-12-27 21:05 GMT+01:00 Alexander Neundorf : > > On Sunday, December 27, 2015 18:40:27 Dimitar Yordanov wrote: > > > Hi all, > > > > > > I was searching for a way to profile CMake scripts in order to find > > > bottlenecks and possibilities to improve performance. I found out