Building and Packaging - Revision history

Arrrghhh at 05:55, 18 January 2012

2012-01-18T05:55:51Z

Arrrghhh: Rejected the last change (by Arrrghhh) and restored revision 1457 by Arrrghhh

2012-01-18T05:52:45Z

Rejected the last change (by Arrrghhh) and restored revision 1457 by Arrrghhh

Arrrghhh: Reverted edits by Arrrghhh (talk) to last revision by Xadmin

2012-01-18T05:51:30Z

Reverted edits by Arrrghhh (talk) to last revision by Xadmin

Arrrghhh at 05:48, 18 January 2012

2012-01-18T05:48:13Z

Arrrghhh: /* Building the System */

2012-01-18T05:47:10Z

Building the System

Xadmin: /* Packaging the System */

2012-01-08T03:16:12Z

Packaging the System

Mgross029: /* Build Dependencies */

2011-12-30T19:45:49Z

Build Dependencies

Mgross029: /* Build Dependencies */

2011-12-30T19:44:22Z

Build Dependencies

Xadmin: /* Packaging the System */

2011-08-28T14:30:50Z

Packaging the System

Raf: system.ext2

2011-06-12T20:47:52Z

system.ext2

← Older revision		Revision as of 05:55, 18 January 2012
Line 34:		Line 34:

	After several weeks, the build will be complete and the system is ready for packaging.		After several weeks, the build will be complete and the system is ready for packaging.
		+
		+	Recent versions of Ubuntu (after 10.04 AFAIK) have [http://code.google.com/p/android/issues/detail?id=20795 a pitfall when building.] Edit <tt>build/core/combo/HOST_linux-x86.mk</tt>:
		+	-HOST_GLOBAL_CFLAGS += -D_FORTIFY_SOURCE=0
		+	+HOST_GLOBAL_CFLAGS += -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0

	==Packaging the System==		==Packaging the System==

@@ Line 38: / Line 38: @@
 The Android build system, which hopefully went off without a hitch, will have generated a number of filesystem images in <tt>out/target/product/msm</tt> under the root directory of the source tree.
-Until development of the system has progressed to the point where the system can be flashed to the phone's integrated flash storage, most of the generated images are of no concern. The most interesting image is <tt>system.img</tt>, which contains the binaries generated by the compilation process.[http://www.gadgetsdotcom.com/ ]
+Until development of the system has progressed to the point where the system can be flashed to the phone's integrated flash storage, most of the generated images are of no concern. The most interesting image is <tt>system.img</tt>, which contains the binaries generated by the compilation process.
-If the recommendations given in [[Build Configuration]] have been followed, the filesystem images will be ext2. This is usable as-is with the current boot process that the XDAndroid project uses, and it can be renamed <tt>[[system.ext2]]</tt> and placed in the user's <tt>andboot</tt> directory for a successful boot.[http://www.seoserviceskingdom.com ]
+If the recommendations given in [[Build Configuration]] have been followed, the filesystem images will be ext2. This is usable as-is with the current boot process that the XDAndroid project uses, and it can be renamed <tt>[[system.ext2]]</tt> and placed in the user's <tt>andboot</tt> directory for a successful boot.
-Optionally, the system image can be repacked as a SquashFS file system, for smaller size. Instructions on completing this step will follow shortly.[http://www.duaan.com ]
+Optionally, the system image can be repacked as a SquashFS file system, for smaller size. Instructions on completing this step will follow shortly.

@@ Line 38: / Line 38: @@
 The Android build system, which hopefully went off without a hitch, will have generated a number of filesystem images in <tt>out/target/product/msm</tt> under the root directory of the source tree.
-Until development of the system has progressed to the point where the system can be flashed to the phone's integrated flash storage, most of the generated images are of no concern. The most interesting image is <tt>system.img</tt>, which contains the binaries generated by the compilation process.
+Until development of the system has progressed to the point where the system can be flashed to the phone's integrated flash storage, most of the generated images are of no concern. The most interesting image is <tt>system.img</tt>, which contains the binaries generated by the compilation process.[http://www.gadgetsdotcom.com/ ]
-If the recommendations given in [[Build Configuration]] have been followed, the filesystem images will be ext2. This is usable as-is with the current boot process that the XDAndroid project uses, and it can be renamed <tt>[[system.ext2]]</tt> and placed in the user's <tt>andboot</tt> directory for a successful boot.
+If the recommendations given in [[Build Configuration]] have been followed, the filesystem images will be ext2. This is usable as-is with the current boot process that the XDAndroid project uses, and it can be renamed <tt>[[system.ext2]]</tt> and placed in the user's <tt>andboot</tt> directory for a successful boot.[http://www.seoserviceskingdom.com ]
-Optionally, the system image can be repacked as a SquashFS file system, for smaller size. Instructions on completing this step will follow shortly.
+Optionally, the system image can be repacked as a SquashFS file system, for smaller size. Instructions on completing this step will follow shortly.[http://www.duaan.com ]

@@ Line 34: / Line 34: @@
 After several weeks, the build will be complete and the system is ready for packaging.
 ==Packaging the System==
 The Android build system, which hopefully went off without a hitch, will have generated a number of filesystem images in <tt>out/target/product/msm</tt> under the root directory of the source tree.
-Until development of the system has progressed to the point where the system can be flashed to the phone's integrated flash storage, most of the generated images are of no concern. The most interesting image is <tt>system.img</tt>, which contains the binaries generated by the compilation process.[http://www.gadgetsdotcom.com/ ]
+Until development of the system has progressed to the point where the system can be flashed to the phone's integrated flash storage, most of the generated images are of no concern. The most interesting image is <tt>system.img</tt>, which contains the binaries generated by the compilation process.
-If the recommendations given in [[Build Configuration]] have been followed, the filesystem images will be ext2. This is usable as-is with the current boot process that the XDAndroid project uses, and it can be renamed <tt>[[system.ext2]]</tt> and placed in the user's <tt>andboot</tt> directory for a successful boot.[http://www.seoserviceskingdom.com ]
+If the recommendations given in [[Build Configuration]] have been followed, the filesystem images will be ext2. This is usable as-is with the current boot process that the XDAndroid project uses, and it can be renamed <tt>[[system.ext2]]</tt> and placed in the user's <tt>andboot</tt> directory for a successful boot.
-Optionally, the system image can be repacked as a SquashFS file system, for smaller size. Instructions on completing this step will follow shortly.[http://www.duaan.com ]
+Optionally, the system image can be repacked as a SquashFS file system, for smaller size. Instructions on completing this step will follow shortly.

← Older revision		Revision as of 05:47, 18 January 2012
Line 34:		Line 34:

	After several weeks, the build will be complete and the system is ready for packaging.		After several weeks, the build will be complete and the system is ready for packaging.
		+
		+	Note - recent versions of Ubuntu (after 10.04 AFAIK) have [http://code.google.com/p/android/issues/detail?id=20795 a pitfall when building.] Edit <tt>build/core/combo/HOST_linux-x86.mk</tt>:
		+	-HOST_GLOBAL_CFLAGS += -D_FORTIFY_SOURCE=0
		+	+HOST_GLOBAL_CFLAGS += -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0

	==Packaging the System==		==Packaging the System==

@@ Line 12: / Line 12: @@
 Camera support requires a modified proprietary binary library, and the system will not build without this library. A zip file containing the library is available as [http://www.mediafire.com/?b2348y0pg9948p4 liboemcamera.zip]. Place that zip in the root of your XDAndroid source tree and '''do not extract it'''.
-Additionally, XDAndroid optionally allows installation of Google's proprietary programs. These programs provide the most popular common features of Android systems. It is usually recommended to install these. A script, located in the device/xdandroid repository of the AOSP build tree, will automatically download the currently-supported Google Apps package, then extract it and configure the build tree to use it. (BookPhone.apk is missing from gapps package and is [http://www.mediafire.com/?6d9zamxw9wwyxyy available here] or Google it and put it into vendor/xdandroid/msm/proprietary)
+Additionally, XDAndroid optionally allows installation of Google's proprietary programs. These programs provide the most popular common features of Android systems. It is usually recommended to install these. A script, located in the device/xdandroid repository of the AOSP build tree, will automatically download the currently-supported Google Apps package, then extract it and configure the build tree to use it. (BookPhone.apk is missing from gapps package and is [http://www.mediafire.com/?6d9zamxw9wwyxyy available here] or Google it then put it into vendor/xdandroid/msm/proprietary)
 With the needed packages stored in the XDAndroid root, run a script to automatically extract the files and configure the build system:

@@ Line 6: / Line 6: @@
 ==Build Dependencies==
-XDAndroid runs on hardware similar to the HTC G1 and Android Dev Phone. As a result, XDAndroid takes advantage of the similarities by using certain proprietary libraries as provided by the reference system for the Dev Phone. Before building the system, download the Dev Phone system image, <tt>signed-dream_devphone_userdebug-ota-14721.zip</tt>, from [http://developer.htc.com/adp.html HTC Developer Center]. Place the zip file in the root of your XDAndroid source tree and '''do not extract it'''.
+XDAndroid runs on hardware similar to the HTC G1 and Android Dev Phone. As a result, XDAndroid takes advantage of the similarities by using certain proprietary libraries as provided by the reference system for the Dev Phone. Before building the system, download the Dev Phone system image, <tt>signed-dream_devphone_userdebug-ota-14721.zip</tt>, is [http://www.mediafire.com/?1gqtzgzmdw4 available here] or Google it. Place the zip file in the root of your XDAndroid source tree and '''do not extract it'''.
-Hardware-accelerated 3D graphics are also available using a proprietary driver originally developed for the HTC Dream. A new driver compatible with gingerbread and later releases, supporting OpenGL-ES version 1.1, is [http://www.mediafire.com/file/b7a6v7eeg8pr3e3/hw3d-20110311.zip available for download]. Place that zip in the root of your XDAndroid source tree and '''do not extract it'''.
+Hardware-accelerated 3D graphics are also available using a proprietary driver originally developed for the HTC Dream. A new driver compatible with gingerbread and later releases, supporting OpenGL-ES version 1.1, is [http://www.mediafire.com/file/zh095lc3czburai/hw3d-20111216.zip available for download]. Place that zip in the root of your XDAndroid source tree and '''do not extract it'''.
 Camera support requires a modified proprietary binary library, and the system will not build without this library. A zip file containing the library is available as [http://www.mediafire.com/?b2348y0pg9948p4 liboemcamera.zip]. Place that zip in the root of your XDAndroid source tree and '''do not extract it'''.
-Additionally, XDAndroid optionally allows installation of Google's proprietary programs. These programs provide the most popular common features of Android systems. It is usually recommended to install these. A script, located in the device/xdandroid repository of the AOSP build tree, will automatically download the currently-supported Google Apps package, then extract it and configure the build tree to use it.
+Additionally, XDAndroid optionally allows installation of Google's proprietary programs. These programs provide the most popular common features of Android systems. It is usually recommended to install these. A script, located in the device/xdandroid repository of the AOSP build tree, will automatically download the currently-supported Google Apps package, then extract it and configure the build tree to use it. (BookPhone.apk is missing from gapps package and is [http://www.mediafire.com/?6d9zamxw9wwyxyy available here] or Google it and put it into vendor/xdandroid/msm/proprietary)
 With the needed packages stored in the XDAndroid root, run a script to automatically extract the files and configure the build system: