next
Shiboken v1.0.2 documentation
»
Next topic
1. Frequently Asked Questions
Quick search
Table of contents
ΒΆ
1. Frequently Asked Questions
1.1. General
1.1.1. What is Shiboken?
1.1.2. Why did you switch from Boost.Python to Shiboken?
1.2. Creating bindings
1.2.1. Can I wrap non-Qt libraries?
1.2.2. Is there any runtime dependency on the generated binding?
1.2.3. What do I have to do to create my bindings?
1.2.4. Is there any recommended build system?
1.2.5. Can I write closed-source bindings with the generator?
1.2.6. What is ‘inject code’?
2. Command line options
2.1. Usage
2.2. Options
3. Type System Variables
3.1. Variables
3.2. Example
4. Code Injection Semantics
4.1. Conventions
4.2. inject-code tag
4.3. Anatomy of Code Injection
4.3.1. Noteworthy Cases
4.4. Code Injection for Functions/Methods
4.4.1. On The Native Side
4.4.2. On The Target Side
4.5. Code Injection for Wrapped Classes
4.5.1. On The Native Side
4.5.2. On The Target Side
4.6. Code Injection for Modules
4.6.1. On The Native Side
4.6.2. On The Target Side
5. Sequence Protocol
6. Object ownership
6.1. Ownership basics
6.2. Invalidating objects
6.2.1. C++ taking ownership
6.2.2. Invalidate after use
6.2.3. Objects with virtual methods
6.3. Parent-child relationship
6.3.1. Parentship heuristics
6.3.2. Return value heuristics
6.4. Common pitfalls
6.4.1. Not saving unowned objects references
7. Words of Advice
7.1. Duck punching and virtual methods
7.2. Python old style classes and PySide