JavaRecipeHowto - Revision history

Eric: Undo revision 3463 by Ejumuvo (Talk)

2010-11-24T09:15:05Z

Undo revision 3463 by Ejumuvo (Talk)

← Older revision	Revision as of 09:15, 24 November 2010
(No difference)

Eric: Undo revision 3279 by Yjytalamago (Talk)

2010-11-24T07:53:16Z

Undo revision 3279 by Yjytalamago (Talk)

← Older revision	Revision as of 07:53, 24 November 2010
(No difference)

Kgilmer: /* Inheriting java-library */

2008-10-03T22:09:59Z

Inheriting java-library

← Older revision		Revision as of 22:09, 3 October 2008
Line 58:		Line 58:

	inherit java-library		inherit java-library

			We need to use another tool called <tt>fastjar-native</tt> which will take our compiled code and create a Jar. In Bitbake the way to describe that you depend on another recipe is the DEPENDS variable:

			DEPENDS = "fastjar-native"

	== Pulling in your Sources ==		== Pulling in your Sources ==

Kgilmer: /* Inheriting java-library */

2008-10-03T22:00:34Z

Inheriting java-library

← Older revision		Revision as of 22:00, 3 October 2008
Line 57:		Line 57:
	The next step is to add the <tt>java-library</tt> functionality into your recipe so that compiling and jarring the code is easy.		The next step is to add the <tt>java-library</tt> functionality into your recipe so that compiling and jarring the code is easy.

	~~inheret~~ java-library		inherit java-library

	== Pulling in your Sources ==		== Pulling in your Sources ==

Kgilmer: /* Pulling in your Sources */

2008-10-03T22:00:02Z

Pulling in your Sources

← Older revision		Revision as of 22:00, 3 October 2008
Line 67:		Line 67:
	Now we have to make a decision about what version we want to build. It is possible to write recipes for different versions of packages. The common practice is to create an ".inc" file that includes common functionality across all the versions. For now we will only be providing one version so this isn't necessary. Looking in the <tt>tags</tt> folder shows that the latest release is 1.0.0 RC3. We will define our <tt>SRC_URI</tt> variable to load sources for this tag:		Now we have to make a decision about what version we want to build. It is possible to write recipes for different versions of packages. The common practice is to create an ".inc" file that includes common functionality across all the versions. For now we will only be providing one version so this isn't necessary. Looking in the <tt>tags</tt> folder shows that the latest release is 1.0.0 RC3. We will define our <tt>SRC_URI</tt> variable to load sources for this tag:

	SRC_URI = "svn://concierge.svn.sourceforge.net/svnroot/concierge/tags/Concierge/1.0.0.RC3/		SRC_URI = "svn://concierge.svn.sourceforge.net/svnroot/concierge/tags/Concierge/1.0.0.RC3/;module=framework;proto=https;rev=220;localdir=${PN}"
	;module=framework;proto=https;rev=220;localdir=${PN}"

	Note the parameters in the string. These parameters are read by BitBake to determine what exactly to download and where to put the sources. <tt>${PN}</tt> defines 'Package Name' and is a good way of keeping recipe code clean and reusable.		Note the parameters in the string. These parameters are read by BitBake to determine what exactly to download and where to put the sources. <tt>${PN}</tt> defines 'Package Name' and is a good way of keeping recipe code clean and reusable.

Kgilmer: /* Pulling in your Sources */

2008-10-03T21:58:57Z

Pulling in your Sources

← Older revision		Revision as of 21:58, 3 October 2008
Line 67:		Line 67:
	Now we have to make a decision about what version we want to build. It is possible to write recipes for different versions of packages. The common practice is to create an ".inc" file that includes common functionality across all the versions. For now we will only be providing one version so this isn't necessary. Looking in the <tt>tags</tt> folder shows that the latest release is 1.0.0 RC3. We will define our <tt>SRC_URI</tt> variable to load sources for this tag:		Now we have to make a decision about what version we want to build. It is possible to write recipes for different versions of packages. The common practice is to create an ".inc" file that includes common functionality across all the versions. For now we will only be providing one version so this isn't necessary. Looking in the <tt>tags</tt> folder shows that the latest release is 1.0.0 RC3. We will define our <tt>SRC_URI</tt> variable to load sources for this tag:

	SRC_URI = "svn://concierge.svn.sourceforge.net/svnroot/concierge/tags/Concierge/1.0.0.RC3/;module=framework;proto=https;rev=220;localdir=${PN}"		SRC_URI = "svn://concierge.svn.sourceforge.net/svnroot/concierge/tags/Concierge/1.0.0.RC3/
			;module=framework;proto=https;rev=220;localdir=${PN}"

	Note the parameters in the string. These parameters are read by BitBake to determine what exactly to download and where to put the sources. <tt>${PN}</tt> defines 'Package Name' and is a good way of keeping recipe code clean and reusable.		Note the parameters in the string. These parameters are read by BitBake to determine what exactly to download and where to put the sources. <tt>${PN}</tt> defines 'Package Name' and is a good way of keeping recipe code clean and reusable.

Kgilmer: /* Pulling in your Sources */

2008-10-03T21:58:37Z

Pulling in your Sources

← Older revision		Revision as of 21:58, 3 October 2008
Line 60:		Line 60:

	== Pulling in your Sources ==		== Pulling in your Sources ==

			An OE variable <tt>SRC_URI</tt> defines where BitBake looks for package sources from. Looking on the Concierge homepage, it appears that the sources live in an svn server here:

			svn://concierge.svn.sourceforge.net/svnroot/concierge

			Now we have to make a decision about what version we want to build. It is possible to write recipes for different versions of packages. The common practice is to create an ".inc" file that includes common functionality across all the versions. For now we will only be providing one version so this isn't necessary. Looking in the <tt>tags</tt> folder shows that the latest release is 1.0.0 RC3. We will define our <tt>SRC_URI</tt> variable to load sources for this tag:

			SRC_URI = "svn://concierge.svn.sourceforge.net/svnroot/concierge/tags/Concierge/1.0.0.RC3/;module=framework;proto=https;rev=220;localdir=${PN}"

			Note the parameters in the string. These parameters are read by BitBake to determine what exactly to download and where to put the sources. <tt>${PN}</tt> defines 'Package Name' and is a good way of keeping recipe code clean and reusable.

	== Testing it out ==		== Testing it out ==

Kgilmer: /* Inheriting java-library */

2008-10-03T21:52:18Z

Inheriting java-library

← Older revision		Revision as of 21:52, 3 October 2008
Line 54:		Line 54:

	== Inheriting <tt>java-library</tt> ==		== Inheriting <tt>java-library</tt> ==

			The next step is to add the <tt>java-library</tt> functionality into your recipe so that compiling and jarring the code is easy.

			inheret java-library

	== Pulling in your Sources ==		== Pulling in your Sources ==

Kgilmer: /* General Items */

2008-10-03T21:43:40Z

General Items

← Older revision		Revision as of 21:43, 3 October 2008
Line 41:		Line 41:

	== General Items ==		== General Items ==

			The first step is to decide where your recipe should live. It's a good idea when adding or modifying recipes to isolate them in such a way that they are easily installed on top of existing OE installations. However for now we will just add our recipe into the Jalimo oe-overlay directory. On my machine this directory is:

			$OEROOT/jalimo/oe-overlay/packages

			In <tt>packages</tt> I will create a directory <tt>concierge</tt> and a file <tt>concierge.bb</tt>. There are a few items that are common to all recipes, some metadata used to identify the package, it's license, and where it comes from. Here is our initial recipe <tt>concierge.bb</tt>:

			DESCRIPTION = "A lightweight R3 OSGi Framework"
			AUTHOR = "Jan Rellermeyer"
			LICENSE = "BSD"
			HOMEPAGE = "http://concierge.sourceforge.net"

	== Inheriting <tt>java-library</tt> ==		== Inheriting <tt>java-library</tt> ==

Kgilmer: /* Java Native Tools */

2008-10-03T21:38:31Z

Java Native Tools

← Older revision		Revision as of 21:38, 3 October 2008
Line 25:		Line 25:

	$ bitbake cacao-native		$ bitbake cacao-native

	...		...

	NOTE: package cacao-native-0.99.3: completed		NOTE: package cacao-native-0.99.3: completed
	NOTE: Tasks Summary: Attempted 265 tasks of which 248 didn't need to be rerun and 0 failed.		NOTE: Tasks Summary: Attempted 265 tasks of which 248 didn't need to be rerun and 0 failed.