LeapFrog Pollux Platform: Build Environment - Revision history

Jrspruitt: /* Environment Variables */

2011-07-07T07:23:44Z

‎Environment Variables

Jrspruitt: /* Environment Variables */

2011-07-07T07:19:48Z

‎Environment Variables

Jrspruitt: /* Environment Variables */

2011-07-07T07:19:34Z

‎Environment Variables

Jrspruitt at 01:05, 7 July 2011

2011-07-07T01:05:24Z

Jrspruitt: /* Installing Software */

2011-07-06T20:01:43Z

‎Installing Software

Jrspruitt: /* Installing Software */

2011-07-06T20:00:13Z

‎Installing Software

Jrspruitt: /* Installing Software */

2011-07-06T19:57:07Z

‎Installing Software

Jrspruitt: Created page with "== Summary == A build environment allows you to compile a kernel, root file system, or programs for use on your device. Commonly referred to as Cross Compiling, this will set up ..."

2011-07-06T19:21:19Z

Created page with "== Summary == A build environment allows you to compile a kernel, root file system, or programs for use on your device. Commonly referred to as Cross Compiling, this will set up ..."

New page

== Summary ==
A build environment allows you to compile a kernel, root file system, or programs for use on your device. Commonly referred to as Cross Compiling, this will set up your Linux host PC to build for a different architecture, in this case the [[Pollux]](LF1000) SoC.

== Software Needed ==
* These are meant to be run on the Linux OS
* [[LeapFrog_Pollux_Platform:_Source_Code#Toolchains| RidgeRun Toolchain]]
* [[LeapFrog_Pollux_Platform:_Source_Code| Source Code]]

== How To ==
=== Installing Software ===
'''RidgeRun toolchain'''

This should be extracted to the /opt directory.

''' Source Code '''
The source code for your particular application can be extracted pretty much anywhere. A project folder in your home directory works well.

In the main folder, that contains the linux-2.6/, packages/, scripts/ directories, create a folder called target/ this is used by the build scripts, and will cause an error if not present.

'''Tip:''' Set it up so you can have multiple source trees parallel to each other. Keep an untouched tree in this directory, along with trees for different major changes you are working on. This makes it easy to create and roll back patches, and keeps modifications organized and sensible.

=== Environment Variables ===
Once you got your toolchain and source code in their respective directories, you'll need to set up some environmental variables for the cross compiling, and the build scripts. The following paths should be copy and pasted into a text file, crosscompile_env_vars, and stored in your source code parent directory.

export WORK_DIR=$PWD
export CROSS_COMPILER_ROOT=/opt/RidgeRun/arm-eabi-uclibc
export PATH=$CROSS_COMPILER_ROOT/bin/:$PATH
export CROSS_COMPILE=arm-linux-
export UBOOT_CROSS_COMPILE=arm-linux-
export TARGET_MACH=LF_LF1000
export ROOTFS_PATH=$WORK_DIR/target/rootfs/
export EROOTFS_PATH=$WORK_DIR/target/erootfs/
export TFTP_PATH=$WORK_DIR/target/tftp/
export RELEASE_PATH=$WORK_DIR/target/release/

You need to use the command line to build the source code, so open up a terminal and go to the source code you want to build. If you run ls you should see linux-2.6/ packages/ and scripts/ from here you want to set your environment variables, as they are set up based on what directory you are in.

source ../crosscompile_env_vars

This will set your current terminal shell with these variables, if you close it, or use another one, you need to reset these variables by running that command.

You are now set up to start compiling for the LeapFrog Pollux Platform.

@@ Line 35: / Line 35: @@
   export TARGET_MACH=LF_LF1000
-  export ROOTFS_PATH=$PROJECT_PATH/target/rootfs/
+  export ROOTFS_PATH=$PROJECT_PATH/target/rootfs
-  export EROOTFS_PATH=$PROJECT_PATH/target/erootfs/
+  export EROOTFS_PATH=$PROJECT_PATH/target/erootfs
-  export TFTP_PATH=$PROJECT_PATH/target/tftp/
+  export TFTP_PATH=$PROJECT_PATH/target/tftp
-  export RELEASE_PATH=$PROJECT_PATH/target/release/
+  export RELEASE_PATH=$PROJECT_PATH/target/release

@@ Line 39: / Line 39: @@
   export TFTP_PATH=$PROJECT_PATH/target/tftp/
   export RELEASE_PATH=$PROJECT_PATH/target/release/
-−
-−
 You need to use the command line to build the source code, so open up a terminal and go to the source code you want to build. If you run ls you should see linux-2.6/ packages/ and scripts/ from here you want to set your environment variables, as they are set up based on what directory you are in.

← Older revision		Revision as of 01:05, 7 July 2011
Line 44:		Line 44:

	You are now set up to start compiling for the LeapFrog Pollux Platform.		You are now set up to start compiling for the LeapFrog Pollux Platform.
		+
		+
		+	[[Category:Didj]]
		+	[[Category:Leapster Explorer]]
		+	[[Category:LeapPad Explorer]]
		+	[[Category:LeapFrog Pollux Platform]]

@@ Line 19: / Line 19: @@
 The source code for your particular application can be extracted pretty much anywhere. A project folder in your home directory works well.
-Depending on how you build the source code, you may need to create a few directories for the build scripts to put the finished images and binaries in. These directories will be TFTP_PATH, ROOTFS_PATH, EROOTFS_PATH, and RELEASE as defined in the environment variables script.
+Depending on how you build the source code, you may need to create a few directories for the build scripts to put the finished images and binaries in. These directories will be TFTP_PATH, ROOTFS_PATH, EROOTFS_PATH, and RELEASE_PATH as defined in the environment variables script.
 '''Tip:''' Set it up so you can have multiple source trees parallel to each other. Keep an untouched tree in this directory, along with trees for different major changes you are working on. This makes it easy to create and roll back patches, and keeps modifications organized and sensible.

@@ Line 26: / Line 26: @@
 Once you got your toolchain and source code in their respective directories, you'll need to set up some environmental variables for the cross compiling, and the build scripts. The following paths should be copy and pasted into a text file, crosscompile_env_vars, and stored in your source code parent directory.
-  export WORK_DIR=$PWD
+  export PROJECT_PATH=$PWD
   export CROSS_COMPILER_ROOT=/opt/RidgeRun/arm-eabi-uclibc
   export PATH=$CROSS_COMPILER_ROOT/bin/:$PATH
   export CROSS_COMPILE=arm-linux-
   export UBOOT_CROSS_COMPILE=arm-linux-
   export TARGET_MACH=LF_LF1000
-  export ROOTFS_PATH=$WORK_DIR/target/rootfs/
-  export EROOTFS_PATH=$WORK_DIR/target/erootfs/
+  export ROOTFS_PATH=$PROJECT_PATH/target/rootfs/
-  export TFTP_PATH=$WORK_DIR/target/tftp/
+  export EROOTFS_PATH=$PROJECT_PATH/target/erootfs/
-  export RELEASE_PATH=$WORK_DIR/target/release/
+  export TFTP_PATH=$PROJECT_PATH/target/tftp/
+  export RELEASE_PATH=$PROJECT_PATH/target/release/
 You need to use the command line to build the source code, so open up a terminal and go to the source code you want to build. If you run ls you should see linux-2.6/ packages/ and scripts/ from here you want to set your environment variables, as they are set up based on what directory you are in.

@@ Line 14: / Line 14: @@
 This should be extracted to the /opt directory.
 ''' Source Code '''
 The source code for your particular application can be extracted pretty much anywhere. A project folder in your home directory works well.
 '''Tip:''' Set it up so you can have multiple source trees parallel to each other. Keep an untouched tree in this directory, along with trees for different major changes you are working on. This makes it easy to create and roll back patches, and keeps modifications organized and sensible.
 === Environment Variables ===