Difference between revisions of "Building a component in OE"
Jump to navigation
Jump to search
(→Setup) |
|||
Line 38: | Line 38: | ||
</pre> | </pre> | ||
− | for the binary you have | + | for the binary you have built and transfer it to the device to the right location. For example use adb |
+ | |||
+ | <pre> | ||
+ | $ adb push tmp-glibc/work/armv7a-vfp-neon-webos-linux-gnueabi/luna-webappmanager/0.2.0-8+gitAUTOINC+5344f19613-r0/build/src/LunaWebAppManager /usr/sbin/ | ||
+ | </pre> |
Revision as of 13:30, 15 January 2015
Setup
Assumptions
- You have a local copy of the component repo in path/to/<component name>
- You have a working OE build dir in /srv/webos-ports (To set this up, start here: [1])
- You have a working knowledge of linux
- You have the Android SDK Setup
Configuration
Add the following to the bottom of conf/local.conf
S_pn-luna-<component name> = "path/to/<component name>"
Building
Now you can build the component from your OE environment by
$ MACHINE=<machine name> bb -c compile -f <component name>
The output is hidden inside the build tree. Look into the path
tmp-glibc/work/armv7a-vfp-neon-webos-linux-gnueabi/<component name>/<version>/build
or
tmp-glibc/work/<machine name>-webos-linux-gnueabi/<component name>/<version>/build
for the binary you have built and transfer it to the device to the right location. For example use adb
$ adb push tmp-glibc/work/armv7a-vfp-neon-webos-linux-gnueabi/luna-webappmanager/0.2.0-8+gitAUTOINC+5344f19613-r0/build/src/LunaWebAppManager /usr/sbin/