Meego Wiki
Views

SDK/Docs/1.0/Packaging MeeGo applications

From MeeGo wiki
(Difference between revisions)
Jump to: navigation, search
Line 9: Line 9:
* An archive of files to be installed on the destination filesystem (e.g. executables, images, documentation)
* An archive of files to be installed on the destination filesystem (e.g. executables, images, documentation)
 +
This [[Packaging/Tutorial]] will give you a whole story to create a rpm package from a qt project.
<!-- To create an RPM package, you need??? -->
<!-- To create an RPM package, you need??? -->
Line 16: Line 17:
* [[Packaging]]
* [[Packaging]]
* [[Packaging/Guidelines]]
* [[Packaging/Guidelines]]
-
* [[Packaging/Tutorial]]
 
* [[Packaging/Deb conversion example]]
* [[Packaging/Deb conversion example]]

Revision as of 12:49, 26 May 2010


To distribute an application to a MeeGo device, it should be packaged using the RPM format. (It is possible to manually copy binaries to a device and get them to run, but this is not recommended, as there is no way to specify dependencies.)

An RPM file is a binary file consisting of:

  • A signature to verify the origin and integrity of the package
  • Metadata (name, version, architecture, authors etc.)
  • An archive of files to be installed on the destination filesystem (e.g. executables, images, documentation)

This Packaging/Tutorial will give you a whole story to create a rpm package from a qt project.

See:

Retrieved from "http://wiki.meego.com/SDK/Docs/1.0/Packaging_MeeGo_applications"
Personal tools