03.05.2022 18:15, Richard Weickelt пишет:
Hi,
My old version works with replacing 'product' on 'exportingProduct':
property var exportIncludePaths: [
"./",
"./shared",
]
cpp.includePaths: exportIncludePaths
Export {
Depends { name: "cpp" }
cpp.includePaths: exportingProduct.exportIncludePaths
}
I am not sure whether you have it working or not. Above pattern works
on my end at least.
According to link
https://codereview.qt-project.org/c/qbs/qbs/+/383049 there was a
change in the definition for variable 'product' inside the section
'Export'. Maybe then you need to display some message in the log
about a change in behavior?
It was a deliberate decision. The topic was first mentioned in:
https://code.qt.io/cgit/qbs/qbs.git/tree/changelogs/changes-1.18.0.md
The "product" variable in Export items was scheduled for removal in
the 1.20 release. The re-introduction of "product", but now as an
alias of "importingProduct" has been mentioned in:
https://code.qt.io/cgit/qbs/qbs.git/tree/changelogs/changes-1.22.0.md
I now have all the projects at work will fall down. People will come
to me and say: "Your 'QBS' doesn't work" (I promote the use of QBS at
my firm).
Can generally prohibit the use of variable 'product' in section
'Export', lag behind only 'importingProduct' and 'exportingProduct'?
Display a message about this in the log.
I am sorry to hear that this change creates inconvenience for you.
What would you suggest to improve in case we have to do such a
breaking change again?
Don't take critics of colleagues personally. You know the problem, you
can help fixing the problem, everybody will be happy. People complain
every day and have already forgotten about it the other day.
Yes, I think all projects will be fixed, everyone with assembly problems
will come to me. I was probably just hurt that in a serious project,
experienced developers allowed such a situation.
If in version 1.20/1.21 I saw a deprecated-message stating that
'product' variable in section 'Export' is no longer supported and should
be replaced with 'exportingProduct', then the problem would not have
arisen. As I understood this transition did not happen spontaneously,
you discussed it over several versions. I propose to display deprecate-
messages in the future that QBS users could respond in a timely manner
to impending changes.
--
BR, Pavel
Cheers
Richard
_______________________________________________
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
_______________________________________________
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
