Package Applications for Tizen: Difference between revisions
AutoSpider (talk | contribs) (Add "cleanup" tag) |
AutoSpider (talk | contribs) (Convert ExpressionEngine links) |
||
| Line 6: | Line 6: | ||
Required steps: | Required steps: | ||
1. Installed | 1. Installed [https://developer.tizen.org/downloads/tizen-sdk Tizen SDK] | ||
2. Generated | 2. Generated [https://developer.tizen.org/help/index.jsp?topic=/org.tizen.gettingstarted/html/dev_env/certificate_generator.htm developer certificate] | ||
3. Qt binaries should have rpath set to application installation lib subdirectory: | 3. Qt binaries should have rpath set to application installation lib subdirectory: | ||
/opt/usr/apps/APP_ID/lib | /opt/usr/apps/APP_ID/lib | ||
Revision as of 15:08, 4 March 2015
| This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
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)