I've used the following a few times recently to get a sense of hotspots:
https://gist.github.com/ihnorton/05f1dea38e596e75ba106855d490e66a
On Wed, Jun 20, 2018 at 10:17 AM Robert Dailey
wrote:
> I set my minimum required version to 3.6, which should enable those
> policies by default (if
I set my minimum required version to 3.6, which should enable those
policies by default (if they're truly in 3.1 as you indicated).
My CMake scripts do a lot of work to build a "tree" of properties
connecting targets, so that I can recurse the targets my system
generates to process things. CMake
I set my minimum required version to 3.6, which should enable those
policies by default (if they're truly in 3.1 as you indicated).
My CMake scripts do a lot of work to build a "tree" of properties
connecting targets, so that I can recurse the targets my system
generates to process things. CMake
I am not aware of any built in functionality that can generate
performance numbers for a project.
Have you made sure that the performance/parsing policies are set to
NEW or your cmake_minimum_required is sufficiently high, those can
have a significant improvement on configuration time.
Polices (
So I noticed over the years my CMake scripts take longer and longer to
configure/generate. Is there a mechanism to tell which parts of my
CMake scripts are slowest? I'd like to know how to optimize my CMake
scripts to reduce the time it takes to generate projects.
--
Powered by www.kitware.com
