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

From Qt Wiki
Jump to navigation Jump to search
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 [https://developer.tizen.org/downloads/tizen-sdk Tizen <span class="caps">SDK</span>] ''[developer.tizen.org]''<br /> 2. Generated [https://developer.tizen.org/help/index.jsp?topic=/org.tizen.gettingstarted/html/dev_env/certificate_generator.htm developer certificate] ''[developer.tizen.org]''<br /> 3. Qt binaries should have rpath set to application installation lib subdirectory:<br /> /opt/usr/apps/APP_ID/lib<br /> where <span class="caps">APP</span>_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 <span class="caps">LFLAGS</span> (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)
1. Installed &quot;Tizen SDK&amp;quot;:https://developer.tizen.org/downloads/tizen-sdk<br />2. Generated &quot;developer certificate&amp;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)


===Categories:===
[[Category:Developing_Qt::Ports::Tizen]]
 
* [[:Category:Developing Qt|Developing_Qt]]
** [[:Category:Developing Qt::Ports|Ports]]
* [[:Category:Developing Qt::Ports::Tizen|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&quot;:https://developer.tizen.org/downloads/tizen-sdk
2. Generated "developer certificate&quot;: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)