blob: 13c0d126592ea0950402b21d177aab70be139413 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
|
tizen-application-manager, how to port into agl-demom-platform for Automotive Grade Linux
==========================================================================
Release note
Application Manager is responsible for
* install/uninstall application
* launch/suspend/resume/kill application
* lifecycle management(event)
* manage application data
* provide application information
The current version of tizen-application-manager provides the following common APIs to developers
* manage the application
- to launch/stop application
- to manage application information of database
* It doesn't provide efl event
ToDo
------------------
* Register first setting(vconf etc.) as systemd service
* Change global user name to aglglobaluser
* Documentation
* Separate the dependencies of capi-*
* Dynamicaly enable to install applications
* Support multiple runtime engine
- remove efl dependencies
- make event distributions selectable in accordance with runtime engines
Layer Dependencies
------------------
URI: git://git.yoctoproject.org/poky
> branch: jethro,
> revision: 118380bc5d01e52b5edc574abb4176f6e70a54a6
URI: git://git.openembedded.org/meta-openembedded
> layer: meta-oe, meta-multimedia, meta-efl, meta-networking, meta-python
> branch: jethro-next or jethro or master
> revision: 8ab04afbffb4bc5184cfe0655049de6f44269990
URI: https://github.com/meta-qt5/meta-qt5.git
> branch: master or jethro
> revision: ea37a0bc987aa9484937ad68f762b4657c198617
URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl
> layer: meta-agl, meta-ivi-common
> branch: master
> revision: baa986abe444dbbfd59b63f6111a058b80891474
> (or later)
URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-agl-demo
> branch: master
> revision: 9a319937529cca7e263e987b85cb9d6fca0b468c
> (or later)
URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-renesas
> layer: meta-rcar-gen2
> branch: agl-1.0-bsp-1.8.0
> revision: 82611ccadef36ab0b8a6fd6fb1cf055e115f1ef5
> (or later)
## The Renesas R-Car Gen2 (Porter) board depends in addition on: ##
URI: https://gerrit.automotivelinux.org/gerrit/AGL/meta-renesas
> branch: agl-1.0-bsp-1.8.0
> revision: 82611ccadef36ab0b8a6fd6fb1cf055e115f1ef5
> (or later)
Supported Machine
-----------------
* Renesas R-Car Gen2 (R-Car M2) - machine: porter
Supported Target of bitbake
------------------------
* `agl-demo-platform-plus-application-manager` The image into which add tizen-application-manager
Downloading the Source
--------------------
You can use repo tool to get all layers which are needed to build AGL Distribution.
Please refer to README in meta-agl-demo or meta-agl
After that getting modified tizen-application-manager
$ git clone https://gerrit.automotivelinux.org/gerrit/staging/tizen-application-manager
Build a R-Car M2 (porter) image
-------------------------------
Please refer to README in meta-agl-demo or meta-agl
Build image
-------------------------------
You can build an image for porter using the following steps:
1. change recipes and security_flags.inc
You can select the following process to setup. 1.b is better to avoid mistakes.
1.a Add the following setting in security_flags.inc
+SECURITY_CFLAGS_pn-efl = "${SECURITY_NO_PIE_CFLAGS}"
+SECURITY_CFLAGS_pn-poppler = "${SECURITY_NO_PIE_CFLAGS}"
1.b Override security_flags.inc
$ cd ${METADIR}/tizen-application-manager/
$ cp(mv) security_flags.inc ${METADIR}/poky/meta/conf/distro/include
2. Run the following command:
$ cd ${METADIR}
$ source meta-agl/scripts/aglsetup.sh -m porter [-b build-porter] agl-demo
3. Modify conf/bblayers
3.1 Remove the meta-agl-bsp line in conf/bblayers.conf
remove ${METADIR}/meta-agl/meta-agl-bsp \
3.2 Add following environment variables in conf/bblayers.conf
BBLAYERS =+ " \
${METADIR}/tizen-application-manager/meta-application-manager \
"
4. Modify conf/local.conf
Nothing
5. bitbake the image
$ bitbake agl-demo-platform-plus-application-manager
Deploying to SD card
-------------------------------
The process to refer to README in meta-agl-demo.
Please change file name to agl-demo-platform-plus-application-manager from agl-demo-platform.
-> --file=agl-demo-platform-plus-application-manager-porter.tar.bz2
How to use application manager
-------------------------------
The following process is how to launch sample application trying whether sample package
can be searched from database.
1. Start up porter board and open the weston-terminal
2. Setting
# vconftool set -t string db/menu_widget/language "en-us"
# useradd aglglobalapp
if required to define password, please set the password you like.
# loginctl enable-linger aglglobalapp
3. Launch sample application from user
# login aglglobalapp
$ launch_app org.tizen.amhelloworld
launch sample appli will fail.
$ pkg_createdb_user
$ pkg_initdb_user
$ launch_app org.tizen.amhelloworld
successfull to launch
4. How to start native application
$ pkgcmd -l // to list all applications available. $ pkginfo --listpkg is also available
$ app_launcher -s <pkgid>
For more information, please access the following URL
https://wiki.tizen.org/wiki/IVI/Tizen-IVI_3.0
|
