Languages/Smoke: Difference between revisions

    From KDE TechBase
    m (Text replace - "<code xml>" to "<syntaxhighlight lang="xml">")
    (Removed old language bar)
    (7 intermediate revisions by 3 users not shown)
    Line 1: Line 1:
    {{Template:I18n/Language Navigation Bar|Development/Languages/Smoke}}
    = Overview =
    = Overview =
    '''SMOKE''' is a introspective wrapper around the Qt and KDE frameworks.
    '''SMOKE''' is a introspective wrapper around the Qt and KDE frameworks.
    Legend has it that SMOKE stands for '''S'''cripting '''M'''eta '''O'''bject '''K'''ompiler '''E'''ngine
    Legend has it that SMOKE stands for '''S'''cripting '''M'''eta '''O'''bject '''K'''ompiler '''E'''ngine


    Not only does it provide wrappers for every function in every class,
    Information about all classes and all methods/functions is stored in
    but it also contains meta-information allowing queries of what
    cross-referencing tables for fast look-ups. Thereby the whole API of a wrapped library can be used.
    functions are available and their arguments and return-types.


    All classes, all methods, with all arguments, along with various flags
    The main purpose of SMOKE is making it easier to write bindings from
    reflecting staticness, virtuality, etc. are stored into
    cross-referencing arrays for fast lookups. One can thus read (and call) the whole
    Qt API by simply reading/searching these arrays.
     
    The main purpose of SMOKE is to make it possible to write bindings from
    scripting languages to Qt and KDE - with an emphasis on ease of use and flexibility.
    scripting languages to Qt and KDE - with an emphasis on ease of use and flexibility.


    You can find out more about SMOKE by checking out the  
    You can find out more about SMOKE by checking out the git repositories of the
    [http://websvn.kde.org/trunk/KDE/kdebindings/ kdebindings module] of KDE's SVN.
    [https://projects.kde.org/projects/kde/kdebindings kdebindings module].


    At the time of writing, the [[Development/Languages/Perl|Perl bindings]], [[Development/Languages/Ruby|Ruby bindings]], [[Development/Languages/Qyoto|C# bindings]] and [[Development/Languages/PHP-Qt|PHP bindings]] are known to use it, you might find valuable usage information there.
    At the time of writing, the [[Development/Languages/Perl|Perl bindings]], [[Development/Languages/Ruby|Ruby bindings]], [[Development/Languages/Qyoto|C# bindings]] and [[Development/Languages/PHP-Qt|PHP bindings]] are known to use it, you might find valuable usage information there.
    Line 47: Line 40:
    = Usage example =
    = Usage example =
    == hello.cpp ==
    == hello.cpp ==
    <code cppqt>
    <syntaxhighlight lang="cpp-qt">
    #include <smoke.h>
    #include <smoke.h>
    #include <smoke/qt_smoke.h>
    #include <smoke/qtcore_smoke.h>
     
    #include <smoke/qtgui_smoke.h>
    #include <iostream>
    #include <iostream>
    #include <string>
    #include <string>
    #include <stdio.h>
    #include <stdio.h>
     
    using namespace std;
    using namespace std;
     
    /*
    /*
      * This class will intercept all virtual method calls and will get
      * This class will intercept all virtual method calls and will get
    Line 64: Line 58:
    {
    {
    public:
    public:
    MySmokeBinding(Smoke *s) : SmokeBinding(s) {}
        MySmokeBinding(Smoke *s) : SmokeBinding(s) {}
    void deleted(Smoke::Index classId, void *obj) {
        void deleted(Smoke::Index classId, void *obj) {
    printf("~%s (%p)\n", className(classId), obj);
            printf("~%s (%p)\n", className(classId), obj);
    }
        }
    bool callMethod(Smoke::Index method, void *obj,
        bool callMethod(Smoke::Index method, void *obj,
    Smoke::Stack /*args*/, bool /*isAbstract*/)
            Smoke::Stack /*args*/, bool /*isAbstract*/)
    {
        {
    Smoke::Method meth = smoke->methods[method];
            Smoke::Method meth = smoke->methods[method];
    string name;
            string name;
    // check for method flags
            // check for method flags
    if (meth.flags & Smoke::mf_protected) name += "protected ";
            if (meth.flags & Smoke::mf_protected) name += "protected ";
    if (meth.flags & Smoke::mf_const) name += "const ";
            if (meth.flags & Smoke::mf_const) name += "const ";
    // add the name
            // add the name
    name += smoke->methodNames[meth.name] + string("(");
            name += smoke->methodNames[meth.name] + string("(");
    // iterate over the argument list and build up the
            // iterate over the argument list and build up the
    // parameter names
            // parameter names
    Smoke::Index *idx = smoke->argumentList + meth.args;
            Smoke::Index *idx = smoke->argumentList + meth.args;
    while (*idx) {
            while (*idx) {
    name += smoke->types[*idx].name;
                name += smoke->types[*idx].name;
    idx++;
                idx++;
    if (*idx) name += ", ";
                if (*idx) name += ", ";
    }
            }
    name += ")";
            name += ")";
    if (name == "protected mousePressEvent(QMouseEvent*)")
            if (name == "protected mousePressEvent(QMouseEvent*)")
    cout << className(meth.classId) << "(" << obj
                cout << className(meth.classId) << "(" << obj
        << ")::" << name << endl;
                    << ")::" << name << endl;
    return false;
            return false;
    }
        }
    /*
        /*
    * In a bindings runtime, this should return the classname as used
        * In a bindings runtime, this should return the classname as used
    * in the bindings language, e.g. Qt::Widget in Ruby or
        * in the bindings language, e.g. Qt::Widget in Ruby or
    * Qyoto.QWidget in C#
        * Qyoto.QWidget in C#
    */
        */
    char *className(Smoke::Index classId) {
        char *className(Smoke::Index classId) {
    return (char*) smoke->classes[classId].className;
            return (char*) smoke->classes[classId].className;
    }
        }
    };
    };
     
    // just for convenience, so we can pass Smoke::ModuleIndexes to std::cout
    // just for convenience, so we can pass Smoke::ModuleIndexes to std::cout
    ostream& operator<<(ostream& lhs, Smoke::ModuleIndex rhs)
    ostream& operator<<(ostream& lhs, Smoke::ModuleIndex rhs)
    {
    {
    lhs << "[" << rhs.smoke->moduleName() << ", " << rhs.index << "]";
        lhs << "[" << rhs.smoke->moduleName() << ", " << rhs.index << "]";
    return lhs;
        return lhs;
    }
    }
     
    int main(int argc, char **argv)
    int main(int argc, char **argv)
    {
    {
    // init the Qt SMOKE runtime
        // init the Qt SMOKE runtime
    init_qt_Smoke();
        init_qtcore_Smoke();
        init_qtgui_Smoke();
    // create a SmokeBinding for the Qt SMOKE runtime
    MySmokeBinding binding(qt_Smoke);
        // create a SmokeBinding for the Qt SMOKE runtime
        MySmokeBinding qtcoreBinding(qtcore_Smoke);
    // find the 'QApplication' class
        MySmokeBinding qtguiBinding(qtgui_Smoke);
    Smoke::ModuleIndex classId = qt_Smoke->findClass("QApplication");
    /* find the methodId. we use a munged method signature, where  
        // find the 'QApplication' class
    * $ is a plain scalar
        Smoke::ModuleIndex classId = qtcore_Smoke->findClass("QApplication");
    * # is an object
        /* find the methodId. we use a munged method signature, where  
    * ? is a non-scalar (reference to array or hash, undef) */
        * $ is a plain scalar
    Smoke::ModuleIndex methId = qt_Smoke->findMethod("QApplication",
        * # is an object
    "QApplication$?");  // find the constructor
        * ? is a non-scalar (reference to array or hash, undef) */
    cout << "QApplication classId: " << classId
        Smoke::ModuleIndex methId = classId.smoke->findMethod("QApplication",
        << ", QApplication($?) methId: " << methId << endl;
            "QApplication$?");  // find the constructor
        cout << "QApplication classId: " << classId
    // get the Smoke::Class
            << ", QApplication($?) methId: " << methId << endl;
    Smoke::Class klass = classId.smoke->classes[classId.index];
        // get the Smoke::Class
    // findMethod() returns an index into methodMaps, which has
        Smoke::Class klass = classId.smoke->classes[classId.index];
    // information about the classId, methodNameId and methodId. we  
    // are interested in the methodId to get a Smoke::Method
        // findMethod() returns an index into methodMaps, which has
    Smoke::Method meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
        // information about the classId, methodNameId and methodId. we  
        // are interested in the methodId to get a Smoke::Method
    Smoke::StackItem stack[3];
        Smoke::Method meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
    // QApplication expects a reference to argc, so we pass it as a pointer
    stack[1].s_voidp = &argc;
        Smoke::StackItem stack[3];
    stack[2].s_voidp = argv;
        // QApplication expects a reference to argc, so we pass it as a pointer
    // call the constructor, Smoke::Method::method is the methodId
        stack[1].s_voidp = &argc;
    // specifically for this class.
        stack[2].s_voidp = argv;
    (*klass.classFn)(meth.method, 0, stack);
        // call the constructor, Smoke::Method::method is the methodId
        // specifically for this class.
    // the zeroth element contains the return value, in this case the
        (*klass.classFn)(meth.method, 0, stack);
    // QApplication instance
    void *qapp = stack[0].s_voidp;
        // the zeroth element contains the return value, in this case the
        // QApplication instance
    // method index 0 is always "set smoke binding" - needed for
        void *qapp = stack[0].s_voidp;
    // virtual method callbacks etc.
    stack[1].s_voidp = &binding;
        // method index 0 is always "set smoke binding" - needed for
    (*klass.classFn)(0, qapp, stack);
        // virtual method callbacks etc.
        stack[1].s_voidp = &qtguiBinding;
    // create a widget
        (*klass.classFn)(0, qapp, stack);
    classId = qt_Smoke->findClass("QWidget");
    methId = qt_Smoke->findMethod("QWidget", "QWidget");
        // create a widget
    cout << "QWidget classId: " << classId
        classId = qtcore_Smoke->findClass("QWidget");
        << ", QWidget() methId: " << methId << endl;
        methId = classId.smoke->findMethod("QWidget", "QWidget");
        cout << "QWidget classId: " << classId
    klass = classId.smoke->classes[classId.index];
            << ", QWidget() methId: " << methId << endl;
    meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
        klass = classId.smoke->classes[classId.index];
    (*klass.classFn)(meth.method, 0, stack);
        meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
    void *widget = stack[0].s_voidp;
    // set the smoke binding
        (*klass.classFn)(meth.method, 0, stack);
    stack[1].s_voidp = &binding;
        void *widget = stack[0].s_voidp;
    (*klass.classFn)(0, widget, stack);
        // set the smoke binding
        stack[1].s_voidp = &qtguiBinding;
    // show the widget
        (*klass.classFn)(0, widget, stack);
    methId = qt_Smoke->findMethod("QWidget", "show");
    cout << "QWidget classId: " << classId << ", show() methId: "
        // show the widget
        << methId << endl;
        methId = classId.smoke->findMethod("QWidget", "show");
    meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
        cout << "QWidget classId: " << classId << ", show() methId: "
    (*klass.classFn)(meth.method, widget, 0);
            << methId << endl;
        meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
    // we don't even need findClass() when we use the classId provided
        (*klass.classFn)(meth.method, widget, 0);
    // by the MethodMap
    methId = qt_Smoke->findMethod("QApplication", "exec");
        // we don't even need findClass() when we use the classId provided
    cout << "QApplication classId: " << qt_Smoke->methodMaps[methId.index].classId
        // by the MethodMap
        << ", exec() methId: " << methId << endl;
        methId = qtgui_Smoke->findMethod("QApplication", "exec");
        cout << "QApplication classId: " << qtgui_Smoke->methodMaps[methId.index].classId
    klass = methId.smoke->classes[methId.smoke->methodMaps[methId.index].classId];
            << ", exec() methId: " << methId << endl;
    meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
        klass = methId.smoke->classes[methId.smoke->methodMaps[methId.index].classId];
    // call QApplication::exec()
        meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
    (*klass.classFn)(meth.method, 0, stack);   
        // call QApplication::exec()
    // store the return value of QApplication::exec()
        (*klass.classFn)(meth.method, 0, stack);   
    int retval = stack[0].s_int;
        // store the return value of QApplication::exec()
    // destroy the QApplication instance
        int retval = stack[0].s_int;
    methId = qt_Smoke->findMethod("QApplication", "~QApplication");
    cout << "QApplication classId: "
        // destroy the QApplication instance
        << qt_Smoke->methodMaps[methId.index].classId
        methId = qtgui_Smoke->findMethod("QApplication", "~QApplication");
        << ", ~QApplication() methId: " << methId << endl;
        cout << "QApplication classId: "
    meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
            << qtgui_Smoke->methodMaps[methId.index].classId
    (*klass.classFn)(meth.method, qapp, 0);
            << ", ~QApplication() methId: " << methId << endl;
        meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
    // destroy the smoke instance
        (*klass.classFn)(meth.method, qapp, 0);
    delete qt_Smoke;
        // destroy the smoke instance
    // return the previously stored value
        delete qtcore_Smoke;
    return retval;
        delete qtgui_Smoke;
        // return the previously stored value
        return retval;
    }
    }
    </code>
    </syntaxhighlight>


    == CMakeLists.txt ==
    == CMakeLists.txt ==
    Line 221: Line 218:
    set(hello_src hello.cpp)
    set(hello_src hello.cpp)
    add_executable(hello ${hello_src})
    add_executable(hello ${hello_src})
    target_link_libraries(hello smokeqt)
    target_link_libraries(hello smokebase smokeqtcore smokeqtgui)
    </pre>
    </pre>
    This assumes that you've installed KDE4 and kdebindings. If you only have SmokeQt installed, you need to adjust the paths accordingly.
    This assumes that you've installed KDE4 and kdebindings. If you only have SmokeQt installed, you need to adjust the paths accordingly.
    Line 234: Line 231:
    For convenience, the options and switches that smokegen requries are stored in an xml-file. Such config files for Qt-based APIs and KDE-based APIs are already installed with the smokeqt and smokekde libs (in <prefix>/share/smokegen). Give them to smokegen with the -config option, as in
    For convenience, the options and switches that smokegen requries are stored in an xml-file. Such config files for Qt-based APIs and KDE-based APIs are already installed with the smokeqt and smokekde libs (in <prefix>/share/smokegen). Give them to smokegen with the -config option, as in


    <code>smokegen -config /usr/share/smokegen/kde-config.xml</code>
    <syntaxhighlight lang="bash">smokegen -config /usr/share/smokegen/kde-config.xml</syntaxhighlight>


    You can extend options, like include dirs, by giving additional parameters on the command line. For example, you can give additional include dirs with the -I flag:
    You can extend options, like include dirs, by giving additional parameters on the command line. For example, you can give additional include dirs with the -I flag:


    <code>smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp</code>
    <syntaxhighlight lang="bash">smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp</syntaxhighlight>


    smokegen --help will show a complete list of possible options. You'll typically only need -I, -dm, -o and sometimes -g (the default generator in the config.xml files is 'smoke', but sometimes you might want to override it with 'dump' to get a list of classes).
    smokegen --help will show a complete list of possible options. You'll typically only need -I, -dm, -o and sometimes -g (the default generator in the config.xml files is 'smoke', but sometimes you might want to override it with 'dump' to get a list of classes).
    Line 244: Line 241:
    smokegen then expects a list of headers after a double dash. Typically we write an 'include-all' header, like Qt does, to simplify matters. It's also the most secure way to conditionally include headers (on different platforms for example) and later get the smoke compilation right. Such an include file could look like this:
    smokegen then expects a list of headers after a double dash. Typically we write an 'include-all' header, like Qt does, to simplify matters. It's also the most secure way to conditionally include headers (on different platforms for example) and later get the smoke compilation right. Such an include file could look like this:


    <code cppqt>
    <syntaxhighlight lang="cpp-qt">
    // the parser doesn't understand the __attribute__ stuff of GCC - disable it for the smokegen run.
    // the parser doesn't understand the __attribute__ stuff of GCC - disable it for the smokegen run.
    #define MYAPP_EXPORT
    #define MYAPP_EXPORT
    Line 259: Line 256:


    #include <subdir/myheader_c.h>
    #include <subdir/myheader_c.h>
    </code>
    </syntaxhighlight>


    So our command line now looks like this:
    So our command line now looks like this:


    <code>smokegen -config /usr/share/smokegen/kde-config.xml \
    <syntaxhighlight lang="bash">smokegen -config /usr/share/smokegen/kde-config.xml \
    -I /usr/include/MyFancyApp -- myapp_includes.h</code>
    -I /usr/include/MyFancyApp -- myapp_includes.h</syntaxhighlight>


    == Setting up the SMOKE generator ==
    == Setting up the SMOKE generator ==
    Line 321: Line 318:
         </classlist>
         </classlist>
    </config>
    </config>
    </code>
    </syntaxhighlight>


    Again, our revised command line looks like this by now:
    Again, our revised command line looks like this by now:


    <code>smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp \
    <syntaxhighlight lang="bash">smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp \
    -smokeconfig smokeconfig.xml -- myapp_includes.h</code>
    -smokeconfig smokeconfig.xml -- myapp_includes.h</syntaxhighlight>


    And this is it. If you run the command (of course it has to be adjusted to use your own headers and classnames), you should end up with a smokedata.cpp and a bunch of x_*.cpp files which you can compile into one libsmokemyapp.so library.
    And this is it. If you run the command (of course it has to be adjusted to use your own headers and classnames), you should end up with a smokedata.cpp and a bunch of x_*.cpp files which you can compile into one libsmokemyapp.so library.

    Revision as of 16:52, 12 March 2012

    Overview

    SMOKE is a introspective wrapper around the Qt and KDE frameworks. Legend has it that SMOKE stands for Scripting Meta Object Kompiler Engine

    Information about all classes and all methods/functions is stored in cross-referencing tables for fast look-ups. Thereby the whole API of a wrapped library can be used.

    The main purpose of SMOKE is making it easier to write bindings from scripting languages to Qt and KDE - with an emphasis on ease of use and flexibility.

    You can find out more about SMOKE by checking out the git repositories of the kdebindings module.

    At the time of writing, the Perl bindings, Ruby bindings, C# bindings and PHP bindings are known to use it, you might find valuable usage information there.

    Versions

    While Smoke works like a charm for Qt3 and Qt4, a modular Smoke2 has been developed which makes it easy to wrap new C++ libraries and plug them together. The result is a noticeable list of technologies available to Smoke-based bindings, as Qt, QtUiTools, QtWebkit, Qtscript, Qscintilla, Qwt, Akonadi, Plasma, KDE, KDevPlatform, KHtml, KTextEditor, Nepomuk, Okular, Phonon, Solid, Soprano

    API Documentation

    Info on the Smoke API is available on our API Documentation page.

    Usage example

    hello.cpp

    #include <smoke.h>
    #include <smoke/qtcore_smoke.h>
    #include <smoke/qtgui_smoke.h>
     
    #include <iostream>
    #include <string>
    #include <stdio.h>
     
    using namespace std;
     
    /*
     * This class will intercept all virtual method calls and will get
     * notified when an instance created by smoke gets destroyed.
     */
    class MySmokeBinding : public SmokeBinding
    {
    public:
        MySmokeBinding(Smoke *s) : SmokeBinding(s) {}
     
        void deleted(Smoke::Index classId, void *obj) {
            printf("~%s (%p)\n", className(classId), obj);
        }
     
        bool callMethod(Smoke::Index method, void *obj,
            Smoke::Stack /*args*/, bool /*isAbstract*/)
        {
            Smoke::Method meth = smoke->methods[method];
            string name;
     
            // check for method flags
            if (meth.flags & Smoke::mf_protected) name += "protected ";
            if (meth.flags & Smoke::mf_const) name += "const ";
     
            // add the name
            name += smoke->methodNames[meth.name] + string("(");
     
            // iterate over the argument list and build up the
            // parameter names
            Smoke::Index *idx = smoke->argumentList + meth.args;
            while (*idx) {
                name += smoke->types[*idx].name;
                idx++;
                if (*idx) name += ", ";
            }
            name += ")";
     
            if (name == "protected mousePressEvent(QMouseEvent*)")
                cout << className(meth.classId) << "(" << obj
                     << ")::" << name << endl;
            return false;
        }
     
        /*
         * In a bindings runtime, this should return the classname as used
         * in the bindings language, e.g. Qt::Widget in Ruby or
         * Qyoto.QWidget in C#
         */
        char *className(Smoke::Index classId) {
            return (char*) smoke->classes[classId].className;
        }
    };
     
    // just for convenience, so we can pass Smoke::ModuleIndexes to std::cout
    ostream& operator<<(ostream& lhs, Smoke::ModuleIndex rhs)
    {
        lhs << "[" << rhs.smoke->moduleName() << ", " << rhs.index << "]";
        return lhs;
    }
     
    int main(int argc, char **argv)
    {
        // init the Qt SMOKE runtime
        init_qtcore_Smoke();
        init_qtgui_Smoke();
     
        // create a SmokeBinding for the Qt SMOKE runtime
        MySmokeBinding qtcoreBinding(qtcore_Smoke);
        MySmokeBinding qtguiBinding(qtgui_Smoke);
     
        // find the 'QApplication' class
        Smoke::ModuleIndex classId = qtcore_Smoke->findClass("QApplication");
        /* find the methodId. we use a munged method signature, where 
         * $ is a plain scalar
         * # is an object
         * ? is a non-scalar (reference to array or hash, undef) */
        Smoke::ModuleIndex methId = classId.smoke->findMethod("QApplication",
            "QApplication$?");  // find the constructor
        cout << "QApplication classId: " << classId
             << ", QApplication($?) methId: " << methId << endl;
     
        // get the Smoke::Class
        Smoke::Class klass = classId.smoke->classes[classId.index];
     
        // findMethod() returns an index into methodMaps, which has
        // information about the classId, methodNameId and methodId. we 
        // are interested in the methodId to get a Smoke::Method
        Smoke::Method meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
     
        Smoke::StackItem stack[3];
        // QApplication expects a reference to argc, so we pass it as a pointer
        stack[1].s_voidp = &argc;
        stack[2].s_voidp = argv;
        // call the constructor, Smoke::Method::method is the methodId
        // specifically for this class.
        (*klass.classFn)(meth.method, 0, stack);
     
        // the zeroth element contains the return value, in this case the
        // QApplication instance
        void *qapp = stack[0].s_voidp;
     
        // method index 0 is always "set smoke binding" - needed for
        // virtual method callbacks etc.
        stack[1].s_voidp = &qtguiBinding;
        (*klass.classFn)(0, qapp, stack);
     
        // create a widget
        classId = qtcore_Smoke->findClass("QWidget");
        methId = classId.smoke->findMethod("QWidget", "QWidget");
        cout << "QWidget classId: " << classId
             << ", QWidget() methId: " << methId << endl;
     
        klass = classId.smoke->classes[classId.index];
        meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
     
        (*klass.classFn)(meth.method, 0, stack);
        void *widget = stack[0].s_voidp;
        // set the smoke binding
        stack[1].s_voidp = &qtguiBinding;
        (*klass.classFn)(0, widget, stack);
     
        // show the widget
        methId = classId.smoke->findMethod("QWidget", "show");
        cout << "QWidget classId: " << classId << ", show() methId: "
             << methId << endl;
        meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
        (*klass.classFn)(meth.method, widget, 0);
     
        // we don't even need findClass() when we use the classId provided
        // by the MethodMap
        methId = qtgui_Smoke->findMethod("QApplication", "exec");
        cout << "QApplication classId: " << qtgui_Smoke->methodMaps[methId.index].classId
             << ", exec() methId: " << methId << endl;
     
        klass = methId.smoke->classes[methId.smoke->methodMaps[methId.index].classId];
        meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
     
        // call QApplication::exec()
        (*klass.classFn)(meth.method, 0, stack);  
     
        // store the return value of QApplication::exec()
        int retval = stack[0].s_int;
     
        // destroy the QApplication instance
        methId = qtgui_Smoke->findMethod("QApplication", "~QApplication");
        cout << "QApplication classId: "
             << qtgui_Smoke->methodMaps[methId.index].classId
             << ", ~QApplication() methId: " << methId << endl;
        meth = methId.smoke->methods[methId.smoke->methodMaps[methId.index].method];
        (*klass.classFn)(meth.method, qapp, 0);
     
        // destroy the smoke instance
        delete qtcore_Smoke;
        delete qtgui_Smoke;
     
        // return the previously stored value
        return retval;
    }
    

    CMakeLists.txt

    find_package(KDE4 REQUIRED)
    
    include_directories(${KDE4_INCLUDE_DIR})
    link_directories(${KDE4_LIB_DIR})
    
    set(hello_src hello.cpp)
    add_executable(hello ${hello_src})
    target_link_libraries(hello smokebase smokeqtcore smokeqtgui)
    

    This assumes that you've installed KDE4 and kdebindings. If you only have SmokeQt installed, you need to adjust the paths accordingly.

    How to create a SMOKE lib

    To generate SMOKE libs for your own libs and APIs, a new tool has been written, called 'smokegen'. It's included in kdebindings since KDE SC 4.4. We're still missing a FindSmokegen.cmake file, but it's being worked on. Still, here's a quick tutorial to generate your own smoke lib:

    smokegen itself only does the parsing of C++ header files, it then expects a plugin which does something useful with the parsed information. Currently there are two plugins (called a 'generator') available: the 'dump' generator, which simply prints the available classes to stdout, and the 'smoke' generator, which actually generates the Smoke source files.

    Setting up the parser

    For convenience, the options and switches that smokegen requries are stored in an xml-file. Such config files for Qt-based APIs and KDE-based APIs are already installed with the smokeqt and smokekde libs (in <prefix>/share/smokegen). Give them to smokegen with the -config option, as in

    smokegen -config /usr/share/smokegen/kde-config.xml
    

    You can extend options, like include dirs, by giving additional parameters on the command line. For example, you can give additional include dirs with the -I flag:

    smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp
    

    smokegen --help will show a complete list of possible options. You'll typically only need -I, -dm, -o and sometimes -g (the default generator in the config.xml files is 'smoke', but sometimes you might want to override it with 'dump' to get a list of classes).

    smokegen then expects a list of headers after a double dash. Typically we write an 'include-all' header, like Qt does, to simplify matters. It's also the most secure way to conditionally include headers (on different platforms for example) and later get the smoke compilation right. Such an include file could look like this:

    // the parser doesn't understand the __attribute__ stuff of GCC - disable it for the smokegen run.
    #define MYAPP_EXPORT
    
    // Since KDE 4.5 this is also supported (and encouraged):
    // #ifdef __SMOKEGEN_RUN__
    // #  define MYAPP_EXPORT
    // #endif
    // This is needed on windows platforms, where MYAPP_EXPORT typically expands
    // to __dllimport and is needed for successful compilation.
    
    #include <myheader_a.h>
    #include <myheader_b.h>
    
    #include <subdir/myheader_c.h>
    

    So our command line now looks like this:

    smokegen -config /usr/share/smokegen/kde-config.xml \
    -I /usr/include/MyFancyApp -- myapp_includes.h
    

    Setting up the SMOKE generator

    Now we still need a smokeconfig.xml for our 'smoke' generator, so that it knows what our modules is called, which parent modules it has, what classes should be included, etc. For elaborate smokeconfig.xml files you can take a look at the ones for the various smoke libs shipped in the kdebindings module, in the subdirs smoke/<moduleName>/smokeconfig.xml. A very simple smokeconfig.xml would look like this:

    <config>
        <moduleName>myapp</moduleName>
    
        <!-- Our classes inherit from classes that are in the kdecore and kdeui modules. -->
        <parentModules>
            <module>kdecore</module>
            <module>kdeui</module>
        </parentModules>
    
        <!-- how many source files should the generator create? -->
        <parts>10</parts>
    
        <!-- the following two sections are needed for every Qt based module! -->
        <scalarTypes>
            <!-- QString is a class, but represented as a scalar (#) in munged names -->
            <typeName>QString</typeName>
        </scalarTypes>
        <voidpTypes>
            <!-- both are classes, but they are represented as Smoke::t_voidp -->
            <typeName>QStringList</typeName>
            <typeName>QString</typeName>
        </voidpTypes>
    
        <!-- regexps for signatures of methods and functions that we don't want
             to be wrapped in the smoke module -->
        <exclude>
            <!-- we don't want these private members in smoke.. -->
            <signature>.*::d_ptr.*</signature>
            <signature>.*::q_ptr.*</signature>
    
            <!-- we also don't want internalFunction(MyType*) in the smoke lib -->
            <signature>.*internalFunction\(MyType\*\).*</signature>
        </exclude>
    
        <!-- regexps for signatures of top-level functions we want to have included -->
        <functions>
            <!-- include functions starting with 'myapp' -->
            <name>^myapp.*</name>
    
            <!-- and operators -->
            <name>.*operator.*</name>
        </functions>
        <classList>
            <class>MyClassA</class>
            <class>MyClassB</class>
            <class>MyNamespaceA::MyClassC</class>
            <class>MyNamespaceA::MyClassC::MyNestedClass</class>
        </classlist>
    </config>
    

    Again, our revised command line looks like this by now:

    smokegen -config /usr/share/smokegen/kde-config.xml -I /usr/include/MyFancyApp \
    -smokeconfig smokeconfig.xml -- myapp_includes.h
    

    And this is it. If you run the command (of course it has to be adjusted to use your own headers and classnames), you should end up with a smokedata.cpp and a bunch of x_*.cpp files which you can compile into one libsmokemyapp.so library.