Closed jim-bcom closed 1 year ago
In order to reduce warnings messages during qmake and build, this warning has been change as a message, as well as other warnings in builddefs/qmake
cf commit 58a42eeac98ffd7b9ed05e1c7d360d0ab9418d0c
Will be available in next release 4.10.0
available in release 4.10.0
PROBLEM In our project we tend to often use default PROJECTDEPLOYDIR and thus we systematically get the folowing warning message:
I reckon it serves a documentation purpose by easing the discoverability of this feature, but maybe we shouldn't get a warning for an expected behavior.
SUGGESTED SOLUTION The code is here.
Keep this message for a more verbose mode For exemple by using remaken
verboseMessage()
enabled byCONFIG += verbose
or QMake log(level, message) at info level, if such a thing exists? (and don't displaywarning:
, but either nothing or smthing likenote:
). Thus the message could then always print the value to which the variable is set, and, if the variable is not set, add the bit explaining that the variable can be defined to override the default path.If so, i'd suggest to do the same this with the previous message:
Since we tend to define this variable in our .pro we don't see it, but instead of using
message()
here, it could only be a verbose message printing the variable value, and optionnally inform the user that it can override the default value if he wants to ?Make the warning() a message(), like in the INSTALLSUBDIR (which could then stay like this). This would remove this message from the Issues windows of the IDE, and keep it clean for actual warnings.
-> Personnally I'm fine with the last solution: just make the warning a message like for INSTALLSUBDIR.
Thanks.