How to package your QT project and install it in the meego System

Introduction

 

This article will teach you how to package your QT project and install it on the meego device. Here, we use an OpenGL project named "Textures" in the QT example as an example. This original project is a QT example without icons that cannot be started from the meego UI. We will make it look more like an independent application.Program, Which can be started directly from the meego application panel and installed on the meego device in RPM package format.

Preparations

The preparation material is an example of QT demo contained in the QT-example package, which is located in/usr/lib/qt4/example/OpenGL/textures.

Copy it to your $ workspace directory as an independent project. It can be either meego SDK chroot or a Linux machine with QT-examples installed.Code:

 

1. CP-A/usr/lib/qt4/examples/OpenGL/textures $ workspace/textures-0.0.1
2. CD $ workspace/textures-0.0.1

Copy code

Add an icon for the program. Here we use the project icon in the example as our application icon.

 

 

1. CP images/side6.png textures.png

Copy code

Add a desktop file so that we can find our program in the meego application panel.

 

 

1. Vim textures. Desktop

Copy code

Content:

 

 

1. [Desktop entry]
2. Name = qtdemotextures
3. Comment = QT demo textures
4. Exec = textures
5. Categories = development;
6. Icon = textures
7. Type = Application
8. Terminal = false
9. Startupnotify = true

Copy code

Edit the textures. Pro file to remove some definitions used in QT example and add icons and desktop installation.

 

 

1. Vim textures. Pro

Copy code

The modified content is as follows:

 

 

1. Headers = glwidget. h \
2. Window. h
3. Sources = glwidget. cpp \
4. Main. cpp \
5. Window. cpp
6. Resources = textures. qrc
7. Qt + = OpenGL
9. # Install
10. # Target. Path = $ [qt_install_examples]/OpenGL/textures
11. # Sources. Files = $ sources $ headers $ resources $ forms textures. Pro Images
12. # Sources. Path = $ [qt_install_examples]/OpenGL/textures
13. Target. Path = $ [install_prefix]/bin
14. Icon. Files = textures.png
15. Icon. Path = $ [install_prefix]/share/icons
16. Desktop. Files = textures. Desktop
17. Desktop. Path = $ [install_prefix]/share/Applications
19. Instols + = target icon Desktop

Copy code

If you want to test it before packaging, you can build and debug it under meego SDK chroot. For details, see meego x86 development on Hello world-Linux.

 

 

1. Qmake prefix =/usr
2. Make
3. Make install

Copy code

Clean up the project, create the source code compressed package, and prepare for packaging.

 

 

1. Make distclean
2. CD ..
3. Tar jcvf textures-0.0.1.tar.bz2 textures-0.0.1

Copy code

Create a spec File

 

Meego recommends that you use the spectacle tool to create a meego spec file or convert an existing spec file to a meego spec file.

Install spectacle

You can install it directly on the meego platform or meego chroot environment.

 

1. Yum install Python-Cheetah
2. Yum install spectacle

Copy code

If you are a proxy, you need to set it before running the preceding command:

 

 

1. Export http_proxy = http: // proxy_server: Port

Copy code

For details about how to install the software on a Linux host, see spectacle installation.

 

Create a yaml package Metadata File

Spectacle uses the package metadata file as the input to generate the meego spec file. This metadata file is in yaml format. For syntax, see Syntax of spectacle yaml.

Create a textures. yaml file under $ workspace/folder.

 

1. Vim $ workspace/textures. yaml

Copy code

The content is as follows:

1. Name: textures
2. Summary: QT demo-OpenGL textures
3. Version: 0.0.1
4. Release: 1
5. GROUP: Development/tools
6. License: lgplv2.1
7. URL: [url = http://qt.nokia.com] http://qt.nokia.com [/url]
8. Sources:
9. -"Registry.name=-registry.version=.tar.bz2"
10. Description: QT demo OpenGL textures
12. Pkgconfigbr:
13. -Qtcore> = 4.6.0
14. -Qtopengl
15. -Qtgui
16. Configure: None
17. Builder: None
18. Files:
19. -"% {_ Bindir}/Textures"
20. -"% {_ Datadir}/applications/*. desktop"
21. -"% {_ Datadir}/icons/*. PNG"

Copy code

The yaml file can also be created from an existing spec file.

 

 

1. Spec2spectacle package_name.spec

Copy code

For details about spectacle usage, see spectacle usage.

 

Generate a spec file from the yaml File

Using the yaml file, it is easy to generate the spec file:

 

1. Specify textures. yaml

Copy code

The generated $ workspace/textures. spec file contains the following content:

 

 

2. #
4. # Do not edit! Generated:
6. # Spectacle version 0.15
8. #
10. #>> Macros
12. # <Macros
16. Name: textures
18. Summary: QT demo-OpenGL textures
20. Version: 0.0.1
22. Release: 1
24. GROUP: amusements/graphics
26. License: lgplv2.1
28. URL: [url = http://qt.nokia.com] http://qt.nokia.com [/url]
30. Source0: registry.name=-registry.version=.tar.bz2
32. Source100: textures. yaml
34. Requires (post): desktop-file-utils
36. Requires (post):/bin/touch
38. Requires (postun): desktop-file-utils
40. Buildrequires: pkgconfig (qtcore)> = 4.6.0
42. Buildrequires: pkgconfig (qtopengl)
44. Buildrequires: pkgconfig (qtgui)
46. Buildrequires: desktop-file-utils
50. % Description
52. Qt demo OpenGL textures
60. % Prep
62. % Setup-Q-N % {name}-% {version}
66. #>> Setup
68. # <Setup
72. % Build
74. #>> Build pre
76. # <Build pre
84. #>> Build post
86. # <Build post
88. % Install
90. Rm-RF % {buildroot}
92. #>> Install pre
94. # <Install pre
98. #>> Install post
100. # <Install post
102. Desktop-file-install -- delete-original \
104. -- Dir % {buildroot} % {_ datadir}/applications \
106. % {Buildroot} % {_ datadir}/applications /*
114. % Post
116. /Bin/touch -- no-create % {_ datadir}/icons/hicolor |:
118. % {_ Bindir}/GTK-Update-icon-Cache \
120. -- Quiet % {_ datadir}/icons/hicolor 2>/dev/null |:
122. Update-desktop-database % {_ datadir}/Applications &>/dev/null |:
126. % Postun
128. /Bin/touch -- no-create % {_ datadir}/icons/hicolor |:
130. % {_ Bindir}/GTK-Update-icon-Cache \
132. -- Quiet % {_ datadir}/icons/hicolor 2>/dev/null |:
134. Update-desktop-database % {_ datadir}/Applications &>/dev/null |:
140. % Files
142. % Defattr (-, root, root ,-)
144. % {_ Bindir}/textures
146. % {_ Datadir}/applications/*. Desktop
148. % {_ Datadir}/icons/*. PNG
150. #> Files
152. # <Files

Copy code

Modify the textures. spec file to add the QT construction information: "build pre" and "Install Post" segments.

 

 

1. #>> Build pre
2. Export Path =/usr/lib/qt4/bin: $ path
3. Qmake prefix =%{_ prefix}
4. # <Build pre

Copy code

 

1. #>> Install post
2. Make install_root = % {buildroot}/usr install
3. # <Install post

Copy code

 

Build RPM under meego SDK chroot

For application developers, it is very easy to directly create packages in the meego SDK chroot environment through rpmbuild.

First, enter the chroot environment.
Install rpmbuild and meego RPM build configuration

 

1. Zypper install rpm-build
2. Zypper install meego-rpm-config

Copy code

 

Copy the source code and spec file to the correct location

 

1. CP textures-0.0.1.tar.bz2 ~ /Rpmbuild/sources/
2. CP textures. yaml ~ /Rpmbuild/sources/
3. CP textures. spec ~ /Rpmbuild/specs/

Copy code

 

Generate RPM package

 

1. Cd ~ /Rpmbuild/specs
2. Rpmbuild-Ba textures. spec

Copy code

This RPM package will be generated in:

 

 

1. ~ // Rpmbuild/RPMS/i586/textures-0.0.1-1.i586.rpm
2. ~ /Rpmbuild/srpms/textures-0.0.1-1.src.rpm

Copy code

 

More rpmbuild use parameter copy: rpmbuild

Create an RPM package without using chroot or obs

For some build or release users, they may want to build RPM packages that do not require the meego SDK chroot environment. The steps are as follows:

Linux

In Linux, a tool called "build" can directly create an RPM package from the spec file.

@ Install build on your host.
@ Create an RPM package using the build tool and spec File

 

1. Sudo build -- repository [url = repository -- arch i686 textures. spec

Copy code

 

This package will be generated in/var/tmp/build-root/home/abuild/rpmbuild/RPMS/AND/var/tmp/build-root/home/abuild/rpmbuild/srpms /directory, you can configure your http_proxy to ensure the repo is successful.

 

1. Export http_proxy = http: // proxy_server: Port

Copy code

Verify RPM package

 

The RPM package can be directly installed on the meego device or in the meego SDK simulation program, copied to the target device or simulator, and run.

 

1. Zypper -- no-GPG-Checks install textures-0.0.1-1.i586.rpm

Copy code

 

In this case, you can find qtdemotextures in programming under applications, which has been included.