[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bindings
Subject:    smokegen on clang - next steps
From:       Chris Burel <chrisburel () gmail ! com>
Date:       2016-12-23 17:07:17
Message-ID: CAPOisTtGhrZeNXJtx9AQgVKhx5DRNKMdev26vtCQnd7t_+ZoeQ () mail ! gmail ! com
[Download RAW message or body]

Hey guys,
I've been doing some work to get PerlQt to work with Qt5, and this means
getting smoke to build with Qt 5, which means getting c++11 support.  To
that end, I've made a version of smokegen that is built on top of LLVM's
libAST, and I have smoke libraries compiling and working for QtCore, QtGui,
and QtWidgets.  I have test builds for a bunch of different Qt, Clang, and
Perl versions working too:
https://travis-ci.org/chrisburel/perlqt/builds/178146192

I haven't done a comprehensive comparison of the output of my new
clang-based smokegen tool versus the old one for the Qt4 libraries, but it
should produce the same library.

I've been working on a fork from the KDE repos, that I've been keeping in
github (because it lets me do non-fast-forward pushes, which is disabled
for the KDE repo).  The code is here:
https://github.com/chrisburel/smokegen
https://github.com/chrisburel/smokeqt
https://github.com/chrisburel/perlqt

I'm thinking of pushing these changes to the KDE repos and making a
reviewboard post for the smokegen and smokeqt changes.

So, does anyone use smokeqt anymore?  Is anyone interested in taking a look
to see if my implementation of smokegen with llvm is legit?

-Chris

[Attachment #3 (text/html)]

<div dir="ltr"><div><div><div><div><div><div>Hey guys,<br></div>I&#39;ve been doing \
some work to get PerlQt to work with Qt5, and this means getting smoke to build with \
Qt 5, which means getting c++11 support.   To that end, I&#39;ve made a version of \
smokegen that is built on top of LLVM&#39;s libAST, and I have smoke libraries \
compiling and working for QtCore, QtGui, and QtWidgets.   I have test builds for a \
bunch of different Qt, Clang, and Perl versions working too:<br><a \
href="https://travis-ci.org/chrisburel/perlqt/builds/178146192">https://travis-ci.org/chrisburel/perlqt/builds/178146192</a><br><br></div>I \
haven&#39;t done a comprehensive comparison of the output of my new clang-based \
smokegen tool versus the old one for the Qt4 libraries, but it should produce the \
same library.<br><br></div>I&#39;ve been working on a fork from the KDE repos, that \
I&#39;ve been keeping in github (because it lets me do non-fast-forward pushes, which \
is disabled for the KDE repo).   The code is here:<br><a \
href="https://github.com/chrisburel/smokegen">https://github.com/chrisburel/smokegen</a><br><a \
href="https://github.com/chrisburel/smokeqt">https://github.com/chrisburel/smokeqt</a><br><a \
href="https://github.com/chrisburel/perlqt">https://github.com/chrisburel/perlqt</a><br><br></div>I&#39;m \
thinking of pushing these changes to the KDE repos and making a reviewboard post for \
the smokegen and smokeqt changes.<br><br></div>So, does anyone use smokeqt anymore?   \
Is anyone interested in taking a look to see if my implementation of smokegen with \
llvm is legit?<br><br></div><div>-Chris<br></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]