Mer/Build/Application Building - Revision history

imported_>amigadave: wikify slightly

2011-02-11T11:28:48Z

wikify slightly

← Older revision		Revision as of 11:28, 11 February 2011
Line 25:		Line 25:

	==Configure your Home Project to Build against Mer==		==Configure your Home Project to Build against Mer==

	When you upload some source the build-dependencies need to be resolved. OBS does this by looking at a build target repository; if the dependency isn't there and that repository has its own build target repository then it looks there... and so on.		When you upload some source the build-dependencies need to be resolved. OBS does this by looking at a build target repository; if the dependency isn't there and that repository has its own build target repository then it looks there... and so on.

Line 39:		Line 40:

	===Setting up Build Repositories : WWW===		===Setting up Build Repositories : WWW===

	* Click on "Home project" in the left navigation bar in the OBS website		* Click on "Home project" in the left navigation bar in the OBS website
	* On the right click on "Add Repository"		* On the right click on "Add Repository"
Line 50:		Line 52:

	===Setting up Build Repositories : CLI===		===Setting up Build Repositories : CLI===

	To change the build target repositories (part of the project metadata):		To change the build target repositories (part of the project metadata):
	osc meta prj home:yourname -e		osc meta prj home:yourname -e

	The XML should look like this (make sure you use your own "name=" value) paying special attention to the <code><repository></code> tags:		The XML should look like this (make sure you use your own "name=" value) paying special attention to the <code><repository></code> tags:
	<~~pre~~>		<source lang="xml">
	<project name="home:yourname">		<project name="home:yourname">
	<title>yourname's Home Project</title>		<title>yourname's Home Project</title>
Line 66:		Line 69:
	</repository>		</repository>
	</project>		</project>
	</~~pre~~>		</source>

	Here is a full set of [[/XML_Build_Targets\|XML Build targets]] for Ubuntu; they aren't needed unless you're doing something clever.		Here is a full set of [[/XML_Build_Targets\|XML Build targets]] for Ubuntu; they aren't needed unless you're doing something clever.

	==Creating Package==		==Creating Package==

	Each package has its own directory in the project and, by default, is built against any build targets for the project.		Each package has its own directory in the project and, by default, is built against any build targets for the project.

	===Creating Package : WWW===		===Creating Package : WWW===

	* Click on "Home project" in the left navigation bar in the OBS website		* Click on "Home project" in the left navigation bar in the OBS website
	* Click on "Add Package"		* Click on "Add Package"
Line 87:		Line 92:

	===Creating Package : CLI===		===Creating Package : CLI===

	Run		Run
	osc meta pkg -e home:<username> <package>		osc meta pkg -e home:<username> <package>
	This will tell the OBS server about the package. It pops up an editor where you can edit the name/description in XML format and then save. The XML appears like this:		This will tell the OBS server about the package. It pops up an editor where you can edit the name/description in XML format and then save. The XML appears like this:
	<~~pre~~>		<source lang="xml">
	<package name="merpad">		<package name="merpad">
	<title>Title of New Package</title>		<title>Title of New Package</title>
Line 118:		Line 124:
	<url>PUT_UPSTREAM_URL_HERE</url>		<url>PUT_UPSTREAM_URL_HERE</url>
	</package>		</package>
	</~~pre~~>		</source>

	==Uploading Source==		==Uploading Source==

	===Uploading Source : WWW===		===Uploading Source : WWW===

	From your Home Project, you should see a "merpad" entry under Packages.		From your Home Project, you should see a "merpad" entry under Packages.
	Select merpad to go to the Package page (you may already be there if you just created it).		Select merpad to go to the Package page (you may already be there if you just created it).
Line 164:		Line 172:

	===Following the build log : WWW ===		===Following the build log : WWW ===

	In the package page under the build target is a [Build Log] entry.		In the package page under the build target is a [Build Log] entry.
	This takes you to a page showing the build log. There are tickboxes to refresh automatically and to autoscroll.		This takes you to a page showing the build log. There are tickboxes to refresh automatically and to autoscroll.
Line 178:		Line 187:

	==Downloading the Binaries==		==Downloading the Binaries==

	Once OBS has run you can download the binaries and install them by hand.		Once OBS has run you can download the binaries and install them by hand.

Line 199:		Line 209:
	Then running the application manager should show your MerPad.		Then running the application manager should show your MerPad.

	=Local Builds=		==Local Builds==
	OBS lets you run a local build on your desktop.		OBS lets you run a local build on your desktop.

Line 231:		Line 241:
	and once there, run arm commands inside the chroot.		and once there, run arm commands inside the chroot.

			=== Co-existing with Scratchbox ===
	== Co-existing with Scratchbox ==

	If you use the OBS local build facility and the scratchbox-1 local builder then you need to know how to teach the two emulators how to co-exist.		If you use the OBS local build facility and the scratchbox-1 local builder then you need to know how to teach the two emulators how to co-exist.

imported_>amigadave: {{Mer}}

2010-09-22T09:28:20Z

← Older revision		Revision as of 09:28, 22 September 2010
Line 1:		Line 1:
			{{Mer}}

	This page assumes you have [[../Install OBS\|installed OBS]] and setup an account.		This page assumes you have [[../Install OBS\|installed OBS]] and setup an account.

Line 257:		Line 259:
	Exec format error		Exec format error
	which means the kernel doesn't understand the binary format of the executable.		which means the kernel doesn't understand the binary format of the executable.

	~~[[Category:Mer]]~~

imported_>ezjd: /* Local Builds */

2009-12-31T22:30:15Z

Local Builds

← Older revision		Revision as of 22:30, 31 December 2009
Line 201:		Line 201:

	Simply checkout a package:		Simply checkout a package:
	osc co home:username/~~maemopad~~		osc co home:username/merpad

	and run:		and run:
	cd home:username/~~maemopad~~		cd home:username/merpad
	osc build MerExtrasStable_MerStable_Ubuntu_9.04 armv5el merpad_1.0-1.dsc		osc build MerExtrasStable_MerStable_Ubuntu_9.04 armv5el merpad_1.0-1.dsc

imported_>ezjd: /* Local Builds */

2009-12-27T00:35:13Z

Local Builds

← Older revision		Revision as of 00:35, 27 December 2009
Line 210:		Line 210:

	This goes to the server to determine where to get the build-depends (remember the build-target stack) and then downloads them to a local cache. Eventually it installs a bootstrap set to a directory and then does a qemu chroot into it and builds the package.		This goes to the server to determine where to get the build-depends (remember the build-target stack) and then downloads them to a local cache. Eventually it installs a bootstrap set to a directory and then does a qemu chroot into it and builds the package.

			Note that the following 2 python modules may be required
			apt-get install python-m2crypto
			apt-get install python-urlgrabber

	Once it is done you should get a line telling you where the deb is:		Once it is done you should get a line telling you where the deb is:

imported_>joenix: /* Creating Package : CLI */

2009-12-08T10:16:13Z

Creating Package : CLI

← Older revision		Revision as of 10:16, 8 December 2009
Line 96:		Line 96:
	HERE		HERE
	</description>		</description>
	<person role="maintainer" userid="~~lbt~~"/>		<person role="maintainer" userid="username"/>
	<person role="bugowner" userid="~~lbt~~"/>		<person role="bugowner" userid="username"/>
	<url>PUT_UPSTREAM_URL_HERE</url>		<url>PUT_UPSTREAM_URL_HERE</url>
	</package>		</package>
Line 112:		Line 112:
	</description>		</description>

	<person role="maintainer" userid="~~lbt~~"/>		<person role="maintainer" userid="username"/>
	<person role="bugowner" userid="~~lbt~~"/>		<person role="bugowner" userid="username"/>
	<url>PUT_UPSTREAM_URL_HERE</url>		<url>PUT_UPSTREAM_URL_HERE</url>
	</package>		</package>

imported_>joenix: /* Setting up Build Repositories : CLI */

2009-12-08T10:05:00Z

Setting up Build Repositories : CLI

← Older revision		Revision as of 10:05, 8 December 2009
Line 49:		Line 49:
	===Setting up Build Repositories : CLI===		===Setting up Build Repositories : CLI===
	To change the build target repositories (part of the project metadata):		To change the build target repositories (part of the project metadata):
	osc meta prj home:~~lbt~~ -e		osc meta prj home:yourname -e

	The XML should look like this (make sure you use your own "name=" value) paying special attention to the <code><repository></code> tags:		The XML should look like this (make sure you use your own "name=" value) paying special attention to the <code><repository></code> tags:

imported_>lbt: /* Creating Package : WWW */

2009-10-31T21:52:29Z

Creating Package : WWW

← Older revision		Revision as of 21:52, 31 October 2009
Line 79:		Line 79:
	(In the XML the name is also fully qualified with a project and :s )		(In the XML the name is also fully qualified with a project and :s )

	Fill in the values in the boxes and save changes.		Fill in the values in the boxes and save changes; we'll use:
			Name: merpad
			Title : merpad
			Description : A test build of Merpad

	===Creating Package : CLI===		===Creating Package : CLI===

84.51.141.236: /* Local Builds */

2009-10-11T23:57:23Z

Local Builds

← Older revision		Revision as of 23:57, 11 October 2009
Line 210:		Line 210:
	Once it is done you should get a line telling you where the deb is:		Once it is done you should get a line telling you where the deb is:
	/scratch3/maemo/Mer/obs/build-MerExtrasStable_MerStable_Ubuntu_9.04-armv5el-merpad/usr/src/packages/DEBS/merpad_1.0-1_armel.deb		/scratch3/maemo/Mer/obs/build-MerExtrasStable_MerStable_Ubuntu_9.04-armv5el-merpad/usr/src/packages/DEBS/merpad_1.0-1_armel.deb

			It will ask for a password at one stage. You can use your local root password for this. If you get an error complaining about a lack of /usr/lib/common_functions, then create a folder in your home folder, cd into it, and then follow the instructions [http://gitorious.org/mer/build HERE] . they should ask you to run the command

			git clone git://gitorious.org/mer/build.git

			in that folder. This will use git to download a newer 'build' tool for you. See the pageafter it has finished, run ''make install'' to install the tool, and then go back and run the osc build step again. It should continue from the password prompt step successfully this time.


	You can also do:		You can also do:

84.57.164.106: /* To create a new package */

2009-08-24T17:17:51Z

To create a new package

← Older revision		Revision as of 17:17, 24 August 2009
Line 15:		Line 15:
	We will use		We will use
	* a name of "merpad" (lowercase); this is the ''package'' name		* a name of "merpad" (lowercase); this is the ''package'' name
	* a title of "MerPad Example"; this is the human title		* a title of "MerPad Example"; this is the human readable title
	* a description of: "A Mer version of Maemopad. Built on OBS by <yourname>"; this is seen upon installation		* a description of: "A Mer version of Maemopad. Built on OBS by <yourname>"; this is seen upon installation

imported_>lbt: added error for search

2009-07-24T09:50:15Z

added error for search

← Older revision		Revision as of 09:50, 24 July 2009
Line 239:		Line 239:
	qemu-binfmt-conf.sh		qemu-binfmt-conf.sh
	to register qemu to handle arm binaries		to register qemu to handle arm binaries

			A typical error signifying you have this issue is
			Exec format error
			which means the kernel doesn't understand the binary format of the executable.

	[[Category:Mer]]		[[Category:Mer]]