Package Applications for Tizen: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Qt applications can be packaged and installed on developer device or emulator. | Qt applications can be packaged and installed on developer device or emulator. | ||
Currently operation is semi-automatic. <br /> Required steps: | Currently operation is semi-automatic.<br />Required steps: | ||
1. Installed | 1. Installed "Tizen SDK&quot;:https://developer.tizen.org/downloads/tizen-sdk<br />2. Generated "developer certificate&quot;:https://developer.tizen.org/help/index.jsp?topic=/org.tizen.gettingstarted/html/dev_env/certificate_generator.htm<br />3. Qt binaries should have rpath set to application installation lib subdirectory:<br />/opt/usr/apps/APP_ID/lib<br />where APP_ID is 10 chars string(alphanumeric)<br />I simply built QT with such prefix but one can also use chrpath (remeber that chrpath can't make rpath longer than initial)<br />4. Also one need to build application executable with OspMain function and proper LFLAGS (see touch example) and .exe extension<br />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) | ||
[[Category:Developing_Qt::Ports::Tizen]] | |||
Revision as of 10:26, 24 February 2015
Qt applications can be packaged and installed on developer device or emulator.
Currently operation is semi-automatic.
Required steps:
1. Installed "Tizen SDK":https://developer.tizen.org/downloads/tizen-sdk
2. Generated "developer certificate":https://developer.tizen.org/help/index.jsp?topic=/org.tizen.gettingstarted/html/dev_env/certificate_generator.htm
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)