Development Environment - Revision history

Rm: /* Building debian packages with qemu and cross-compiling distccs */

2010-07-20T16:36:38Z

‎Building debian packages with qemu and cross-compiling distccs

Lindi: CONCURRENCY_LEVEL really only works with make-kpkg

2009-03-03T12:45:01Z

CONCURRENCY_LEVEL really only works with make-kpkg

Lindi: how stable-tracking kernels are built

2008-12-03T00:45:50Z

how stable-tracking kernels are built

Lindi: dpkg-buildpackage -aarmel

2008-12-03T00:42:34Z

dpkg-buildpackage -aarmel

Lindi: qemubuilder

2008-12-03T00:40:48Z

qemubuilder

Lindi: document how debian packages can be built with qemu and cross-compiling distcc

2008-12-03T00:37:39Z

document how debian packages can be built with qemu and cross-compiling distcc

Owen: /* Develop with OE */

2008-09-28T18:31:23Z

‎Develop with OE

Owen: /* Develop with OE */

2008-09-28T18:27:58Z

‎Develop with OE

Owen: /* Develop with OE */

2008-09-28T18:26:31Z

‎Develop with OE

Owen: /* Develop with OE */

2008-09-28T18:23:05Z

‎Develop with OE

@@ Line 80: / Line 80: @@
 ) ssh to an ARM with debian unstable. This can be your freerunner but
      you probably want to use
-     e.g. http://people.debian.org/~aurel32/qemu/arm/ with qemu. Note
+     e.g. http://people.debian.org/~aurel32/qemu/armel/ with qemu. Note
      that you probably want to add e.g. "-redir tcp:5022::22" qemu
      option so that you can "ssh localhost -p 5022 -l root" to access

@@ Line 88: / Line 88: @@
 .3) export DISTCC_HOSTS="$address_of_pc1 $address_of_pc2 ..."
 .4) you can now use make -j6 to distribute build to cross-compilers
-.5) note that with debian package you can "CONCURRENCY_LEVEL=6
+.5) note that "apt-get --build" does not support passing parallel build options so
-      apt-get --build source $package" to make sure options are passed
+       you need to split build into to parts: first "apt-get source $package" and then
-       to whatever build system the package uses.
+      "cd $package* && dpkg-buildpackage -j6"
-−
 == Cross-compiling simple debian packages ==

@@ Line 100: / Line 100: @@
   dpkg-buildpackage -aarmel -rfakeroot -us -uc
 might work. See http://iki.fi/lindi/debian/pool/main/a/agps-online for an example of such a simple package.
 [[Category:Application Developer]]

← Older revision		Revision as of 00:42, 3 December 2008
Line 93:		Line 93:


		+	== Cross-compiling simple debian packages ==
		+
		+	If you are lucky something as simple as
		+	apt-get source foo
		+	cd foo*
		+	dpkg-buildpackage -aarmel -rfakeroot -us -uc
		+	might work. See http://iki.fi/lindi/debian/pool/main/a/agps-online for an example of such a simple package.

	[[Category:Application Developer]]		[[Category:Application Developer]]

@@ Line 42: / Line 42: @@
 * Use quilt patches and add it to the bb file.  Rebuild.
 * bitbake openmoko-sample2 -c package_write
 == Building debian packages with qemu and cross-compiling distccs ==
@@ Line 87: / Line 91: @@
        apt-get --build source $package" to make sure options are passed
        to whatever build system the package uses.
-−
 [[Category:Application Developer]]

@@ Line 9: / Line 9: @@
 = Develop with OE =
-After setting up the OE (OpenEmbedded) environment, making it build the latest component of Openmoko is necessary to avoid duplicated work.  Refer to [[Openmoko2007.2#How_to_enable_autorev|How to enable autorev]] to find out how to do this.  The first build will take a lot of time and occupy a good deal of disk space, but after that it will be reasonable.  You will also need to '''remove''' the
+After setting up the OE (OpenEmbedded) environment, making it build the latest component of Openmoko is necessary to avoid duplicated work.  Refer to [[Openmoko2007.2#How_to_enable_autorev|How to enable autorev]] to find out how to do this.  The first build will take a lot of time and occupy a good deal of disk space, but after that it will be faster.  You will also need to '''remove''' the
   INHERIT += "rm_work
 line in your local.conf if it exists.

@@ Line 9: / Line 9: @@
 = Develop with OE =
-After setting up the OE environment, making it build the latest component of Openmoko is a must to avoid duplicated work.  Refer to [[Openmoko2007.2#How_to_enable_autorev|How to enable autorev]] to find out how to do it.  Building for the first time will take a lot of time and occupy big disk space, but after that it will be reasonable.  You will also need to '''remove''' the
+After setting up the OE(OpenEmbedded) environment, making it build the latest component of Openmoko is a must to avoid duplicated work.  Refer to [[Openmoko2007.2#How_to_enable_autorev|How to enable autorev]] to find out how to do it.  Building for the first time will take a lot of time and occupy big disk space, but after that it will be reasonable.  You will also need to '''remove''' the
   INHERIT += "rm_work
 line in your local.conf if it exists.
@@ Line 34: / Line 34: @@
 == Tips ==
-* You might find it convenient to replace the source directory with a symlink to the same directory under your Openmoko svn tree, once you get more understanding to OE.  You need to patch and configure the source again if you go this way.
+* You might find it convenient to replace the source directory with a symlink to the same directory under your Openmoko svn tree, once you get more understanding of OE.  You need to patch and configure the source again if you go this route.
-* If you don't want to use devshell, change directory to ${WORKDIR} directly (usually one level higher then the directory that devshell drops you to), do the modification, and invoke ./temp/run.do_compile.xxxx will also compile the source again.
+* If you don't want to use devshell, change directory to ${WORKDIR} directly (usually one level higher than the directory that devshell drops you to), do the modification, and invoke ./temp/run.do_compile.xxxx will also compile the source again.
 == Make ipkg for distributing ==