Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
Package Applications for Tizen: Difference between revisions
m (Wieland moved page Packaging-Applications to Package Applications for Tizen: better title) |
(Cleanup) |
||
| Line 1: | Line 1: | ||
{{ | {{LangSwitch}} | ||
[[Category:Developing_Qt::Ports::Tizen]] | |||
Qt applications can be packaged and installed on developer device or emulator. | Qt applications can be packaged and installed on developer device or emulator. | ||
| Line 14: | Line 14: | ||
4. Also one need to build application executable with OspMain function and proper LFLAGS (see touch example) and .exe extension | 4. Also one need to build application executable with OspMain function and proper LFLAGS (see touch example) and .exe extension | ||
5. When everything is prepared just need to invoke prepare_tpk (from tizenbuildtools/scripts) and then native-packaging (correct command will be printed after invoking prepare_tpk) | 5. When everything is prepared just need to invoke prepare_tpk (from tizenbuildtools/scripts) and then native-packaging (correct command will be printed after invoking prepare_tpk) | ||
Revision as of 21:11, 28 June 2015
En Ar Bg De El Es Fa Fi Fr Hi Hu It Ja Kn Ko Ms Nl Pl Pt Ru Sq Th Tr Uk Zh
Qt applications can be packaged and installed on developer device or emulator.
Currently operation is semi-automatic. Required steps:
1. Installed Tizen SDK 2. Generated developer certificate 3. Qt binaries should have rpath set to application installation lib subdirectory: /opt/usr/apps/APP_ID/lib where APP_ID is 10 chars string(alphanumeric) I simply built QT with such prefix but one can also use chrpath (remeber that chrpath can't make rpath longer than initial) 4. Also one need to build application executable with OspMain function and proper LFLAGS (see touch example) and .exe extension 5. When everything is prepared just need to invoke prepare_tpk (from tizenbuildtools/scripts) and then native-packaging (correct command will be printed after invoking prepare_tpk)