Package Applications for Tizen: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
(Cleanup layout, spelling, corrected outgoing links)
 
(5 intermediate revisions by 3 users not shown)
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.
 
Following procedure is currently required:
Currently operation is semi-automatic.
# Install [https://developer.tizen.org/downloads/tizen-sdk Tizen SDK]
Required steps:
# Generate a certificate, see [https://developer.tizen.org/documentation/development-tools/common-tools/certificate-registration Certificate Registration] and [https://developer.tizen.org/trouble-shooting-certification Certification Trouble Shooting]
 
# 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). It is also possible to use chrpath, but length of initial rpath must not be exceeded.
1. Installed "Tizen SDK":https://developer.tizen.org/downloads/tizen-sdk
# The executable needs to be built with OspMain and proper LFLAGS (see touch example) and .exe extension
2. Generated "developer certificate":https://developer.tizen.org/help/index.jsp?topic=/org.tizen.gettingstarted/html/dev_env/certificate_generator.htm
# Invoke '''prepare_tpk''' (from tizenbuildtools/scripts)
3. Qt binaries should have rpath set to application installation lib subdirectory:
# The last print from prepare_tpk will be the command for the native-packaging (given there are no errors)
/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)


[[Category:Developing_Qt::Ports::Tizen]]
[[Category:Developing_Qt::Ports::Tizen]]

Latest revision as of 07:09, 30 June 2015

Qt applications can be packaged and installed on developer device or emulator. Following procedure is currently required:

  1. Install Tizen SDK
  2. Generate a certificate, see Certificate Registration and Certification Trouble Shooting
  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). It is also possible to use chrpath, but length of initial rpath must not be exceeded.
  4. The executable needs to be built with OspMain and proper LFLAGS (see touch example) and .exe extension
  5. Invoke prepare_tpk (from tizenbuildtools/scripts)
  6. The last print from prepare_tpk will be the command for the native-packaging (given there are no errors)