Details
-
Suggestion
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
some future version
-
None
Description
Editing global toolchain profiles is painful with the current built-in equipment. While it is possible to use an export/import roundtrip approach for manual editing, it doesn't feel comfortable either.
Instead, why not support profiles specified in a QML file? This would be very user-friendly, efficient, and qt.
Example:
Profile {
name : "bla"
final : true // inheritance is impossible
readOnly : true // can not be overwritten
baseProfile : "myProfile"
Affects { name : "cpp" }
cpp.commonCompilerFlags : "xxx"
}
QML profiles are not supposed to replace current profile configuration. Instead, they could serve as starting point, being read initially before applying other preferences.
