On 01.06.19 17:56, Thiago Macieira wrote:
On Saturday, 1 June 2019 03:46:34 PDT André Pönitz wrote:
I am getting mildly irritated by those ongoing suggestions (not just
yours) to use anything but Qt to get stuff done, even Qt's own tasks.
It's sending an odd message.
Sure, one can pull e.g. any "plain C++" replacement for QXmlStreamReader
for rcc. With the usual non-Qt approaches this means either some other
3rd party dependency or some ad-hoc implementation providing the
part of XML parsing rcc actually needs, or to switch over to another
.qrc format.
At the end of the day, all that would be doable, but *why*?
I'm not suggesting we drop the Qt code from those tools. I'm suggesting that
we un-bootstrap them after we make QtCore not require them at all.
If I can get powershell to produce a C-consumable hex dump of the file, we can
get rid of rcc as a QtCore dependency. But rcc as a tool remains.
I also managed to get that done with a <10 lines of "plain cmake":
https://github.com/woboq/moc-ng/blob/7cfa2b65efaf836054977e5974f8f9c23b0cb057/src/CMakeLists.txt#L46-L54
_______________________________________________
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
