Designer configurations
-
I have a project that I downloaded and built using the 6.4 MSVC2019_64 tooling and Qt Creator (this is pretty much the 1st time I've used it). It initially built a shared library (dll) but that was readily changed bu adding staticlib to the opening line of the .pro file so that it read:
CONFIG += c++20 staticlib
When I asked it to build all configurations, it created three output folders:
<prjname >Desktop_Qt_6_4_0_MSVC2019_64bit-Debug
<prjname >Desktop_Qt_6_4_0_MSVC2019_64bit-Profile
<prjname >Desktop_Qt_6_4_0_MSVC2019_64bit-ReleaseIs this the expected default behaviour?
In what way does the Profile folder differ from the Debug folder
D.
-
I have a project that I downloaded and built using the 6.4 MSVC2019_64 tooling and Qt Creator (this is pretty much the 1st time I've used it). It initially built a shared library (dll) but that was readily changed bu adding staticlib to the opening line of the .pro file so that it read:
CONFIG += c++20 staticlib
When I asked it to build all configurations, it created three output folders:
<prjname >Desktop_Qt_6_4_0_MSVC2019_64bit-Debug
<prjname >Desktop_Qt_6_4_0_MSVC2019_64bit-Profile
<prjname >Desktop_Qt_6_4_0_MSVC2019_64bit-ReleaseIs this the expected default behaviour?
In what way does the Profile folder differ from the Debug folder
D.
@Perdrix
The "Profile" configuration is for building your app for profiling --- instrumentation/timing analysis --- and this requires different compile or link options. Creator allows you to build & run for profiling. Under Linux this uses theperftool. I have no idea what it might or might not do under Windows/MSVC.
