Difference between revisions of "Compile Software for the Humax"
(→Compiling on-box) |
|||
| Line 1: | Line 1: | ||
| − | |||
== Compiling on-box == | == Compiling on-box == | ||
| Line 13: | Line 12: | ||
== Cross compiling on an external host == | == Cross compiling on an external host == | ||
| + | |||
| + | == Recommended ''configure'' parameters == | ||
| + | |||
| + | <pre> | ||
| + | CFLAGS="-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" \ | ||
| + | ./configure \ | ||
| + | --prefix=/mod \ | ||
| + | --host=mipsel-linux \ | ||
| + | --target=mipsel-linux \ | ||
| + | --disable-nls | ||
| + | </pre> | ||
Revision as of 11:01, 18 August 2011
Compiling on-box
It is possible to compile some software directly on the Humax itself, however due to the limited amount of CPU horsepower available, this is only recommended for fairly small packages.
First you need to install the gcc and gawk packages. gcc is the compiler itself and automatically pulls in dependant packages, gawk is needed to properly support packages which use GNU autoconf, which most do.
humax# opkg install gcc gawk
After this, close your telnet session and create a new one to properly set up the environment, and you are ready to compile your first piece of software on the Humax.
Cross compiling on an external host
Recommended configure parameters
CFLAGS="-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" \
./configure \
--prefix=/mod \
--host=mipsel-linux \
--target=mipsel-linux \
--disable-nls
