Hi, I for one would welcome a C++ rewrite of syncqt inside qmake to get rid of the perl dependency. However I do not have the authority to approve such a contribution. It is something we have talked about many times on the hallway.
Until we arrive in the promised land of a new build system, it would allow us to simplify our source packaging even further the moment we have it (syncqt C++). Simon > On 7 Mar 2017, at 08:11, Thiago Macieira <[email protected]> wrote: > > Em segunda-feira, 6 de março de 2017, às 23:32:42 CET, Jake Petroules > escreveu: >>> Yes, we do. We've had that dependency for 15 years. >> >> And it will go away once Qt moves to Qbs as its default build system in Qt >> 6. > > There has been no discussion of qbs. Therefore, there is no decision on what > ot use for Qt 6. It might be cmake or qmake. > > But if we do use a tool that is not part of Qt's sources, it would be nice to > use one that does support generating the headers. I don't find it likely to > find > a generator that will allow the powerful scanning that syncqt.pl does, unless > like syncqt.pl it is actually a fully-featured language with an extensive > library. > > Like Scons (which I'd hate to use, but at this point it is a contender just > as > likely). > >>>> On later steps qt is built pretty good without any serious issues. >>>> >>>> Is there any attempts to rewrite syncqt.pl in c++? >>> >>> No. >> >> >> It will be "rewritten" (although the replacement will not be a direct >> translation) in JavaScript when Qt moves to Qbs. > > Or a cmake script or a Python routine in Scons. > > Or left as-is. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
