Toolchain - Revision history

Fox Mulder: /* Building Openmoko Kernel from git repo using Toolchain */

2010-07-06T19:55:47Z

‎Building Openmoko Kernel from git repo using Toolchain

Zeroedout: change to proper path as in above example

2009-11-13T09:39:14Z

change to proper path as in above example

Zeroedout: /* Troubleshooting */ Needed that to get toolchain to compile- still

2009-11-13T05:26:33Z

‎Troubleshooting: Needed that to get toolchain to compile- still

Numann at 21:42, 25 August 2009

2009-08-25T21:42:23Z

Numann at 21:40, 25 August 2009

2009-08-25T21:40:24Z

Hackerb9: /* Prerequisites */ s/triade/triad/

2009-06-10T07:52:40Z

‎Prerequisites: s/triade/triad/

Aapo: fixing typo

2009-05-03T11:00:16Z

fixing typo

Nowic: /* Building a sample project */ not needed

2009-05-01T17:49:58Z

‎Building a sample project: not needed

Nowic: /* Installing New Libraries */

2009-04-13T23:41:59Z

‎Installing New Libraries

Gorbusch: /* Installing New Libraries */

2009-04-11T12:30:54Z

‎Installing New Libraries

@@ Line 284: / Line 284: @@
 ==Building Openmoko Kernel from git repo using Toolchain==
-You may build the newest 2.6.28 kernel with these commands:
+Explained in more detail at [[Kernel#Building_the_2.6.32_branch]].
-−
- git clone git://git.openmoko.org/git/kernel.git linux-2.6
- cd linux-2.6
- git checkout -b mystable origin/andy-tracking
- mkdir GTA02
- cp arch/arm/configs/gta02-moredrivers-defconfig GTA02/.config
- ./build GTA02 dummy
-−
-The ''dummy'' option is required for the modules to be nicely packaged into a .tar.gz package that can be extracted on the target, in addition to flashing/installing the kernel. The "dummy" just means "some parameter given", for which there is a check in the code eventually for some reason...
-−
-You may need to edit the ./build script for the toolchain directory.
-−
-Read more information about the different branches of Openmoko's Linux kernel at: http://git.openmoko.org/?p=kernel.git;a=summary
-−
-A different approach explained in more detail can be found at [[Howto compile Openmoko kernel for Neo Freerunner]].
-−
-=== Old troubleshooting information ===
-−
-If it fails with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:
-−
- export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"
-−
-to:
-−
- export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -rpath-link ${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -O1"
-−
-I also had to change the 'build' script to hardcode the path to the compiler.
 ==Using toolchain provided libraries==

@@ Line 405: / Line 405: @@
 === Old troubleshooting information ===
-If it fails with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/setup-env is modified. LDFLAGS should be changed from:
+If it fails with error message "arm-angstrom-linux-gnueabi-ld: unrecognized option '-Wl,-rpath-link,/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib'" until /usr/local/openmoko/arm/bin/setup-env is modified. LDFLAGS should be changed from:
   export LDFLAGS="-L${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-rpath-link,${OMTOOL_DIR}/arm/arm-angstrom-linux-gnueabi/lib -Wl,-O1"

@@ Line 403: / Line 403: @@
 * Please use the [http://lists.openmoko.org/mailman/listinfo/openmoko-devel Openmoko-Devel] mailing list.
 [[Category:Application Developer]]
 [[Category:Application Developer]]

@@ Line 78: / Line 78: @@
 * On Debian-based systems (e.g. Ubuntu), you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:
-    bunzip2 openmoko-*-armv4t-linux-gnueabi-toolchain.tar.bz2
+    bunzip2 openmoko-*-armv4t-linux-gnueabi-toolchain*.tar.bz2
-    gzip openmoko-*-armv4t-linux-gnueabi-toolchain.tar
+    gzip openmoko-*-armv4t-linux-gnueabi-toolchain*.tar
-    fakeroot alien -d openmoko-*-armv4t-linux-gnueabi-toolchain.tar.gz
+    fakeroot alien -d openmoko-*-armv4t-linux-gnueabi-toolchain*.tar.gz
     sudo dpkg -i openmoko-*-armv4t-linux-gnueabi-toolchain*.deb

@@ Line 78: / Line 78: @@
 * On Debian-based systems (e.g. Ubuntu), you can use alien(+fakeroot) to create an easy-to-uninstall package from this .tar.bz2:
-    bunzip2 openmoko-*-arm-linux-gnueabi-toolchain.tar.bz2
+    bunzip2 openmoko-*-armv4t-linux-gnueabi-toolchain.tar.bz2
-    gzip openmoko-*-arm-linux-gnueabi-toolchain.tar
+    gzip openmoko-*-armv4t-linux-gnueabi-toolchain.tar
-    fakeroot alien -d openmoko-*-arm-linux-gnueabi-toolchain.tar.gz
+    fakeroot alien -d openmoko-*-armv4t-linux-gnueabi-toolchain.tar.gz
-    sudo dpkg -i openmoko-*-arm-linux-gnueabi-toolchain*.deb
+    sudo dpkg -i openmoko-*-armv4t-linux-gnueabi-toolchain*.deb
 * The prebuilt toolchain is for x86_64 or i686. If you wanted, you could build it on your own with OE, using [[BitBake]]:

@@ Line 17: / Line 17: @@
 You should be reasonably familiar with Linux and its command line tools, have an x86-compatible computer with at least 1G of free disk space. You should have experience with compiling programs from source using your local compiler. The remainder of this document will also assume you have write access in your home directory (~) and <tt>/usr/local/</tt> (becoming root if needed). If any of this is not the case, please call your local administrator for help.
-Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triade of '''./configure, make, make install''').
+Last but not least you should have a working setup that allows you to compile native software packages using the autotools build system (the triad of '''./configure, make, make install''').
 A (partial) list of required packages -- please append as necessary:

← Older revision		Revision as of 17:49, 1 May 2009
Line 147:		Line 147:

	. /usr/local/openmoko/arm/bin/setup-env		. /usr/local/openmoko/arm/bin/setup-env
−
−	* I came to the conclusion that more has to be done before the next step.
−
−	~~opkg-target update~~
−	~~opkg-target install libedje-dev~~
−	~~opkg-target install packagekit-dev~~
−	~~opkg-target install edbus-dev~~
−	~~opkg-target install libetk-dev~~
−	~~opkg-target install libts-dev~~

	* One can chown -R <your-name>.<your-name> /usr/local/openmoko/arm, and		* One can chown -R <your-name>.<your-name> /usr/local/openmoko/arm, and

@@ Line 104: / Line 104: @@
 ==Installing New Libraries==
-Openmoko toolchain doesn't include many libraries by default. However, it can download and install libraries that already exist in the Openmoko repository. It refers to the [http://downloads.openmoko.org/repository/testing/ Testing Repository] by default. There are wrong address in /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf. Check what you have, and modify if needed. You can check with browser what you want to use http://downloads.openmoko.org/repository/
+Openmoko toolchain doesn't include many libraries by default. However, it can download and install libraries that already exist in the Openmoko repository. It refers to the [http://downloads.openmoko.org/repository/testing/ Testing Repository] by default. There are wrong address in /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf. Check what you have, and modify if needed. You can check with your browser what you want to use: http://downloads.openmoko.org/repository/
   #Some working example. /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/etc/opkg.conf

@@ Line 123: / Line 123: @@
 *First, update the opkg database (Notice, you should use alias '''opkg-target''' and <b><i>not</i></b> '''opkg'''. If you get an "Could not obtain administrative lock" error, try to become root with "sudo su" and don't forget to rerun the scripts to set your environment variables if necessary.)
   opkg-target update
 *Second, select a package that you want. Let's use edje as an example. If you want to develop a project which use edje of Enlightenment, you can use '''opkg-target list''' to print out how many packages you can have. Of course, command '''grep''' will help you a lot. (Remember, you should install the -dev package and not only libedje.)