29 | | Weather the on-device Qt version can be used, or custom Qt version needs to be used to run !modRana still needs to be determined. If using the on-device version is possible, the resulting installation package would be quite a bit smaller as the Qt libraries would not need to be included. |
| 29 | Weather the on-device Qt version can be used, or custom Qt version needs to be used to run modRana still needs to be determined. If using the on-device version is possible, the resulting installation package would be quite a bit smaller as the Qt libraries would not need to be included. |
| 30 | |
| 31 | ==== Making sure the right Qt is used ==== |
| 32 | By default (when just running the bbndk environment script before build), Shiboken & !PySide pick-up the Qt libraries that are included in the BB10NDK target, completely ignoring your local Qt build. |
| 33 | |
| 34 | If you want for both Shiboken & PySide to use the proper build, you need to modify ''PATH'' & ''LD_LIBRARY_PATH'' so that it is preferred to the one in the BB10NDK target: |
| 35 | |
| 36 | {{{ |
| 37 | source <BB10NDK PATH>/bbndk-env.sh |
| 38 | export QTDIR=<PATH TO YOUR CUSTOM Qt BUILD> |
| 39 | export LD_LIBRARY_PATH="$QTDIR/lib:$LD_LIBRARY_PATH" |
| 40 | export PATH="$QTDIR/bin:$PATH" |
| 41 | }}} |
| 42 | |
| 43 | You need to either run this in your shell (or put it in a script ''source'' it to your shell) before issuing the ''configure'' commands for Shiboken & !PySide. |