Details
-
Suggestion
-
Resolution: Out of scope
-
P3: Somewhat important
-
None
-
Qt Creator 2.6.2
-
OSX
Description
I'm porting a large commercial project which has multiple configurations: demo, standard, professional etc with debug and release versions for each.
These are configures in the top-level subdir like this:
config_standard_full {
message("**STANDARD FULL CONFIG**")
DEFINES += STANDARD_VERSION
}
else:config_pro_full {
message("**PRO FULL CONFIG**")
DEFINES += PRO_VERSION
} else {
error("no configuration specified")
}
When I import the .pro into Creator, it ignores these configurations completely. Instead, I have to go to the project screen and add -config config_standard_full etc to qmake invocation for the debug and release configurations and then clone those build configurations for the other configs.
This is very laborious for 10 or 20 configurations which must be created by going through dialogs.
Worse, when Creator is updated or the Qt installation is changed, or the project needs to be checked out to another machine, Creator insist on re-generating the .pro.user file containing these configurations so it all has to be done again!
Creator should be able to pick up the build configurations from the .pro file and populate the .pro.user file appropriately.
Attachments
For Gerrit Dashboard: QTCREATORBUG-8803 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
123975,1 | QmakeProject: Allow the user to specificy build configurations in .pro file | master | qt-creator/qt-creator | Status: ABANDONED | 0 | 0 |