Geek Answers Handbook

What does an assembly configuration profile do?

I just upgraded to Qt 5.6.0. I noticed something that I had not noticed before. The new project in Qt Creator now includes three build configurations: release, debugging, and profile. It seems to me that the "profile" is new. If so, what is its purpose?

+6
source share
2 answers

When I looked at projects -> build steps -> qmake efficient call, I found additional CONFIGS:

"CONFIG+=force_debug_info" "CONFIG+=separate_debug_info"

I also found some comments for them that could clarify why this is necessary:

Hello everybody,

once again I am preparing a Qt 5 build for profiling and again wondering why there is no way to combine -release and -debug in a Qt configure script. The only way to get a reasonable build for profiling the Qt code itself, which I know that hack mkspec and ensures that -g is even added to -reserve mode.

Is there a reason for this? Could we somehow improve this situation by simplifying the Qt assembly using optimizations and debugging symbols?

Am I missing the recommended way to do this?

This option creates release builds (with all compiler optimizations), but with debugging symbols (pdb files) that are needed to test C ++ performance.

+5
source

According to Qt's online documentation (Breadcrumb: “Qt User Guide”> “Specifying Build Settings”, end of paragraph 1):

Profile configuration - This is an optimized version of the assembly that comes with separate debugging information. It is best suited for analyzing applications.

The link can be found here . I'm still a Qt newbie and have never personally used this configuration.

0
source

More articles:


All Articles