Porting guide - Revision history

Sebt3 at 21:42, 9 August 2012

2012-08-09T21:42:03Z

ABC: cat

2011-04-19T15:30:08Z

cat

Hitnrun: /* Configure Scripts */

2010-07-18T14:02:45Z

‎Configure Scripts

Cosam: Set category

2010-06-01T10:54:17Z

Set category

Cosam: Initial version

2010-06-01T10:53:53Z

Initial version

New page

This is a placeholder for information about porting existing software to the Pandora.

== Build Environment ==
Ensure you have [[Setting up a cross-compiler|Set up your cross-compiler]].

== Configure Scripts ==
Much open source software comes with a ''configure'' script which can be used to customise the build. Running ''./configure --help'' will usually display all the available options. Most ''configure'' scripts have a ''--host'' option which can be used for cross compiling. The majority of the remaining options can be used to enable or disable features, or to specify where libraries and their headers are located.

== Makefiles ==
If the Makefile for your software aren't generated by a ''configure'' script, it may be necessary to alter parameters manually. Again, the main thing is making sure your cross-compiler is used instead of that on your PC. This is often achieved by setting variables such as CC, LD and similar.

== Helper Programs ==
Some software uses custom tools to aid in the build process. Usually these are built along with the main application itself and compiled as required. Of course, when cross-compiling, these helper programs cannot be run on the PC if they're being compiled for the Pandora. Some ''configure'' scripts are smart enough to allow a native compiler to be used for such programs. In other cases they may need to be built manually. This is easily achieved by compiling the package natively and copying the executables over to the cross-compile build directory.

@@ Line 16: / Line 16: @@
 == Helper Programs ==
 Some software uses custom tools to aid in the build process. Usually these are built along with the main application itself and compiled as required. Of course, when cross-compiling, these helper programs cannot be run on the PC if they're being compiled for the Pandora. Some ''configure'' scripts are smart enough to allow a native compiler to be used for such programs. In other cases they may need to be built manually. This is easily achieved by compiling the package natively and copying the executables over to the cross-compile build directory.
 [[Category:Development]]
 [[Category:Ports]]
 [[Category:Tutorials]]

← Older revision		Revision as of 15:30, 19 April 2011
Line 18:		Line 18:

	[[Category:Development]]		[[Category:Development]]
		+	[[Category:Ports]]
		+	[[Category:Tutorials]]

← Older revision		Revision as of 10:54, 1 June 2010
Line 12:		Line 12:
	== Helper Programs ==		== Helper Programs ==
	Some software uses custom tools to aid in the build process. Usually these are built along with the main application itself and compiled as required. Of course, when cross-compiling, these helper programs cannot be run on the PC if they're being compiled for the Pandora. Some ''configure'' scripts are smart enough to allow a native compiler to be used for such programs. In other cases they may need to be built manually. This is easily achieved by compiling the package natively and copying the executables over to the cross-compile build directory.		Some software uses custom tools to aid in the build process. Usually these are built along with the main application itself and compiled as required. Of course, when cross-compiling, these helper programs cannot be run on the PC if they're being compiled for the Pandora. Some ''configure'' scripts are smart enough to allow a native compiler to be used for such programs. In other cases they may need to be built manually. This is easily achieved by compiling the package natively and copying the executables over to the cross-compile build directory.
		+
		+	[[Category:Development]]

@@ Line 6: / Line 6: @@
 == Configure Scripts ==
 Much open source software comes with a ''configure'' script which can be used to customise the build. Running ''./configure --help'' will usually display all the available options. Most ''configure'' scripts have a ''--host'' option which can be used for cross compiling. The majority of the remaining options can be used to enable or disable features, or to specify where libraries and their headers are located.
 == Makefiles ==