Difference between revisions of "Building a component in OE"

From WebOS-Ports
Jump to navigation Jump to search
Line 5: Line 5:
 
'''Assumptions'''
 
'''Assumptions'''
  
You have a local copy of the component repo in path/to/<component name>
+
* 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: [http://www.webos-ports.org/wiki/Galaxy_Nexus_Build_Setup])
You have a working OE build dir in /srv/webos-ports (To set this up, start here: [http://www.webos-ports.org/wiki/Galaxy_Nexus_Build_Setup])
+
* You have a working knowledge of linux
 
+
* You have the Android SDK Setup
You have a working knowledge of linux
 
 
 
You have the Android SDK Setup
 
 
 
You have your galaxy nexus rndis setup and working.
 
  
 
'''Configuration'''
 
'''Configuration'''
Line 20: Line 15:
  
 
<pre>
 
<pre>
S_pn-luna-sysmgr = "path/to/<component name>"
+
S_pn-luna-<component name> = "path/to/<component name>"
 
</pre>
 
</pre>
  

Revision as of 13:29, 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 build and transfer it to the device