Building Apps and Kernels - Revision history

Lunohod: Fixed link to the How_To_Build_Xecutah

2011-09-23T22:29:40Z

Fixed link to the How_To_Build_Xecutah

Olodin: external link -> internal link to pdk

2011-09-06T07:05:52Z

external link -> internal link to pdk

Cyclic: /* Libraries */

2011-09-03T18:11:53Z

Libraries

Cyclic at 18:07, 3 September 2011

2011-09-03T18:07:33Z

Cyclic: /* Libraries */

2011-09-03T17:57:13Z

Libraries

Cyclic: /* Libraries */

2011-09-03T17:55:36Z

Libraries

Cyclic at 05:49, 3 September 2011

2011-09-03T05:49:05Z

Cyclic: Added info for libraries.

2011-09-03T05:47:58Z

Added info for libraries.

Cyclic at 15:11, 29 August 2011

2011-08-29T15:11:36Z

Cyclic: Added Samples

2011-08-29T15:10:45Z

Added Samples

← Older revision		Revision as of 22:29, 23 September 2011
Line 120:		Line 120:
	== '''Samples''' ==		== '''Samples''' ==

−	After you run through the WIDK and setup your toolchain, take a look at [[~~Application:Xecutah~~]] for details on building X Server and the process for building an application.	+	After you run through the WIDK and setup your toolchain, take a look at [[How_To_Build_Xecutah]] for details on building X Server and the process for building an application.

@@ Line 2: / Line 2: @@
 == '''Setup''' ==
-Depending on what you're building you might need some of the prereq's from here:
+Depending on what you're building you might need some of the prereq's from [[WebOS Internals PDK]] installation.
 Create the directory structure for the source:

@@ Line 66: / Line 66: @@
 Each directory here is a separate library. The library folder contains a Makefile, which links to other Makefiles.  The Makefiles download source for the library and compile the various dependencies of the library that kicked off the make command.
-Let's start by simply compiling xproto and take a look at the different pieces involved in getting the library to compile properly.  If you crack open the Makefile for xproto:
+Let's start by simply compiling libxcb and take a look at the different pieces involved in getting the library to compile properly.  If you crack open the Makefile for libxcb:
 <pre>
 nano /srv/preware/cross-compile/packages/common/x/libxcb/Makefile
 </pre>
-You should see the name of the project, the version number for xproto (this is used to download the package from the tar) and the SRC_BZ2 url.  The SRC_BZ2 url can be changed to point to the package that you're looking to compile.
+You should see the name of the project, the version number for libxcb (this is used to download the package from the tar) and the SRC_BZ2 url.  The SRC_BZ2 url can be changed to point to the package that you're looking to compile.
 <pre>
 NAME = libxcb

@@ Line 91: / Line 91: @@
 </pre>
 '''Note:''' some packages might need additional work to compile (e.g. compiling libxcb requires that you create the full path for the documentation before it will install properly /usr/local/share/doc/libxcb/tutorial).
 Making and packaging builds the goods, packages them for you in a neat little ipkg and places the code where it needs to go for other apps and libraries to link to.  That's about all there is to it!

@@ Line 59: / Line 59: @@
 You might also be interested in using additional libraries in your projects. Your best bet for getting the latest source is to look in the locations of the existing libraries used in other packages.
-First, you it's a good idea to take a look at the directories for all of the common libraries that were downloaded when you setup your toolchain:
+It's a good idea to first take a look at the directories for all of the common libraries that were downloaded when you setup your toolchain:
 <pre>
 cd /srv/preware/cross-compile/packages/common/x

@@ Line 55: / Line 55: @@
 Once you have your toolchain configured and you have had a chance to get your SB2 cross compiler working with one of the applications above, you might be looking to add libraries or compile libraries and "stage" them into your cross compiler /usr directory. The /usr directory in your toolchain is the directory that contains the lib files and include files necessary to compile libraries or applications against the toolchain. Since the TouchPad is targeting armv7, we have to compile libraries to target the armv7 architecture and stage them into the architecture's root /usr/lib and include directories.
-You might also be interested in using additional libraries in your projects. Your best bet is to locate source for your code in some of the existing libraries used in other packages.  Let's start by simply compiling libxcb and take a look at the different pieces involved in getting the library to compile properly.
+Don't worry, once you get the hang of it, it's pretty straight forward. You just have to trust that this is the fastest and easiest way to pull down code, compile dependencies, and get the ball rolling on your own library or application.
-First, you might want to take a look at the directories for all of the common libraries already downloaded when you setup your toolchain:
+You might also be interested in using additional libraries in your projects. Your best bet for getting the latest source is to look in the locations of the existing libraries used in other packages.
 <pre>
 cd /srv/preware/cross-compile/packages/common/x
 ls
 </pre>
-Each directory here is a separate library. The library folder contains a Makefile, which links to other make files for both downloading source for the library and various dependencies of your project.  Don't worry, once you get the hang of it, it's pretty straight forward. You just have to trust that this is the fastest and easiest way to pull down code, compile dependencies, and get the ball rolling on your own library or application.
+Each directory here is a separate library. The library folder contains a Makefile, which links to other Makefiles.  The Makefiles download source for the library and compile the various dependencies of the library that kicked off the make command.
-If you crack open the Makefile for xproto you should see the name of the project, the version number for xproto (this is used to download the package from the tar) and the SRC_BZ2 url (you can change this URL to point to the package that you're looking to compile:
+Let's start by simply compiling xproto and take a look at the different pieces involved in getting the library to compile properly.  If you crack open the Makefile for xproto:
 <pre>
 nano /srv/preware/cross-compile/packages/common/x/libxcb/Makefile
 </pre>
 <pre>
 NAME = libxcb
@@ Line 81: / Line 84: @@
 </pre>
-For most instances, the above text is the only text you will need to modify (for most cases where you need to compile your own library folder in the packages directory).  The process is pretty straight forward from here. Just keep in mind, any folder you list in the DEPENDS section will need to exist and have a Makefile containing similar logic as the makefile you created for the library that lists it in its Makefile depends section.
+For most instances, the above text is the only text you will need to modify (for most cases where you need to compile your own library folder in the packages directory).  The process is pretty straight forward from here. Keep in mind, any folder you list in the DEPENDS section will need to exist and have a Makefile containing similar logic as the makefile you created for the library that lists it in its Makefile depends section.
-If you want to test out compiling and staging (installing it into your target architecture /usr/lib and include folder like we mention above), just type:
+If you want to test out compiling and staging (installing the library into your target architecture /usr/lib and include folder like we mention above), just type:
 <pre>
 make stage package
 </pre>
 Making and packaging builds the goods, packages them for you in a neat little ipkg and places the code where it needs to go for other apps and libraries to link to.  That's about all there is to it!

@@ Line 51: / Line 51: @@
 ) press the Volume Up key and power on the device, you should see a giant USB logo on the device<br>
 ) novacom boot mem:// < uImage
 == '''Notes''' ==

@@ Line 64: / Line 64: @@
 ln -s <location of toolchain> arm-2009q1
 </pre>
 == '''Samples''' ==
 After you run through the WIDK and setup your toolchain, take a look at [[Application:Xecutah]] for details on building X Server and the process for building an application.

← Older revision		Revision as of 15:10, 29 August 2011
Line 64:		Line 64:
	ln -s <location of toolchain> arm-2009q1		ln -s <location of toolchain> arm-2009q1
	</pre>		</pre>
		+
		+
		+	== '''Samples''' ==
		+
		+	After you run through the WIDK and setup your toolchain, take a look at [[Application:Xecutah]] for details on building X Server and the process for building an application.