Skip to content

Use shiboken, not generatorrunner as default generator when building Mobility #7

Open
@mschubert

Description

@mschubert

Issue:
When no generator (-DGENERATOR) is specificed, PySide Mobility tries to use generatorrunner by default. This yields a compilation error in both latest release and Git head:

$ cd pyside-mobility-0.2.3/QtMobility/Contacts && /usr/bin/generatorrunner --generatorSet=shiboken snip
/usr/bin/generatorrunner: Error loading generator-set plugin: shiboken_generator module not found.

$ cd pyside-mobility-0.2.3/QtMobility/Contacts && /usr/bin/generatorrunner --generatorSet=/usr/lib/libshiboken-python2.7.so snip
/usr/bin/generatorrunner: Error loading generator-set plugin: Cannot resolve symbol "getGenerators" in /usr/lib/libshiboken-python2.7.so: (/usr/lib/libshiboken-python2.7.so: undefined symbol: getGenerators)

Workaround:
add the -DGENERATOR=shiboken flag when calling CMAKE

Resolution:
use shiboken as default instead of generatorrunner

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions