Changes between Version 20 and Version 21 of Getting started developing SHR

Timestamp:

04/25/11 18:44:49 (2 years ago)

Author:

jama

Comment:

--

Getting started developing SHR

@@ -31 +31 @@
 Applied to our goal, which is to develop locally SHR applications, you must override four variables: SRC_URI (where does source come from), SRCREV (source revision), SRCPV (program version) and S (working directory when compiling).
 
-To do that, create or edit '''conf/local-builds.inc''' with the following content (i.e libframeworkd-phonegui-efl):
+To do that, create or edit '''conf/local-builds.inc''' with the following content (i.e libphone-ui-shr):
 {{{
-SRC_URI_pn-libframeworkd-phonegui-efl = "file:///path/to/shr-apps"
-SRCREV_pn-libframeworkd-phonegui-efl = "LOCAL"
-SRCPV_pn-libframeworkd-phonegui-efl = "LOCAL"
-S_pn-libframeworkd-phonegui-efl = "${WORKDIR}/shr-apps/shr/${PN}"
+INHERIT_append_pn-libphone-ui-shr = "srctree gitpkgv"
+SRCREV_pn-libphone-ui-shr = "${GITSHA}"
+S_pn-libphone-ui-shr = "/path/to/source/${PN}"
 }}}
-This will cause the directory pointed to by SRC_URI (`shr-apps` in the example) to be copied to ${WORKDIR} for compilation, and the actual source of the application (i.e., the directory where `./configure` and `make` will be run) is expected to be found in S. If unset, S defaults to `${WORKDIR}/${PN}-${PV}`.
 
+then change working directory to folder with your local checkout and you should be able to build it
+{{{
+cd /path/to/source/${PN}
+bitbake -c clean libphone-ui-shr
+bitbake libphone-ui-shr
+}}}
 
 To know the best practice to contribute SHR, please refer to [wiki:"Coding Conventions"].