Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
mschubert opened this issue Aug 30, 2012 · 0 comments

Comments

@mschubert
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant