benlau
20-03-2005, 14:26
hi,
I just wrote a howto(draft) on building madplay. I hope it is useful for whose who would like to compile this software by themself.
Any comments are welcomed. :)
Source: http://benlau.e-fever.org/modules/wiwimod/index.php?page=BuildingMadplayHowto&sel_lang=english
Building madplay for WL500G Howto (Draft)
Prerequisites:
This Howto assumes a build environment of custom firmware 1.9.2.7-4 has been setup according to the instructions provided in Oleg's page of "ASUS WL-500g custom firmware page". It should also work for other versions, but it is not tested.
Download
madplay-0.15.2b.tar.gz
http://sourceforge.net/project/showfiles.php?group_id=12349
libid3tag-0.15.1b.tar.gz
http://sourceforge.net/project/showfiles.php?group_id=12349
libmad-0.15.1b.tar.gz
http://sourceforge.net/project/showfiles.php?group_id=12349
zlib-1.2.2.tar.gz
http://sourceforge.net/project/showfiles.php?group_id=5624
Libraries preparation:
ASUS firmware build package do not come with all the libraries required by madplay, therefore it must build and install them by yourself.
Warning: Below instructions will install additional libraries under the toolchain's path.
Environment variable:
TOOLCHAIN_PATH=/opt/brcm/hndtools-mipsel-uclibc
(This environment variable is not really necessary in the build process. It is used to indicate the target installation path that passes to configure script.)
zlib:
tar zxf zlib-1.2.2.tar.gz
cd zlib-1.2.2
./configure --prefix=$TOOLCHAIN_PATH
make CC=mipsel-uclibc-gcc 2>&1 | tee build.log
make install
libid3tag:
tar zxf libid3tag-0.15.1b.tar.gz
cd libid3tag-0.15.1b
RANLIB=mipsel-uclibc-ranlib AR=mipsel-uclibc-ar CC=mipsel-uclibc-gcc ./configure --prefix=$TOOLCHAIN_PATH --enable-static --disable-shared --host=mips-linux
make 2>&1 | tee build.log
make install
libmad:
tar zxf libmad-0.15.1b.tar.gz
cd libmad-0.15.1b
RANLIB=mipsel-uclibc-ranlib AR=mipsel-uclibc-ar CC=mipsel-uclibc-gcc CXX=mipsel-uclibc-g++ ./configure --prefix=$TOOLCHAIN_PATH --enable-static --host=mips-linux --disable-shared
make 2>&1 | tee build.log
make install
madplay compilation:
After installed all the libraries provided above, you could now compile madplay:
tar zxf madplay-0.15.2b.tar.gz
cd madplay-0.15.2b
LIBS="-lm -lz" RANLIB=mipsel-uclibc-ranlib AR=mipsel-uclibc-ar CC=mipsel-uclibc-gcc CXX=mipsel-uclibc-g++ ./configure --prefix=$TOOLCHIAN_PATH --enable-static --host=mips-linux
make 2>&1 | tee build.log
If no error was found during the compilation, a binary file (`madplay`) should be created within the path of madplay-0.15.2b/ . As additional libraries like libmad and id3tag are linked statically, you could just install this single binary to your access point.
I just wrote a howto(draft) on building madplay. I hope it is useful for whose who would like to compile this software by themself.
Any comments are welcomed. :)
Source: http://benlau.e-fever.org/modules/wiwimod/index.php?page=BuildingMadplayHowto&sel_lang=english
Building madplay for WL500G Howto (Draft)
Prerequisites:
This Howto assumes a build environment of custom firmware 1.9.2.7-4 has been setup according to the instructions provided in Oleg's page of "ASUS WL-500g custom firmware page". It should also work for other versions, but it is not tested.
Download
madplay-0.15.2b.tar.gz
http://sourceforge.net/project/showfiles.php?group_id=12349
libid3tag-0.15.1b.tar.gz
http://sourceforge.net/project/showfiles.php?group_id=12349
libmad-0.15.1b.tar.gz
http://sourceforge.net/project/showfiles.php?group_id=12349
zlib-1.2.2.tar.gz
http://sourceforge.net/project/showfiles.php?group_id=5624
Libraries preparation:
ASUS firmware build package do not come with all the libraries required by madplay, therefore it must build and install them by yourself.
Warning: Below instructions will install additional libraries under the toolchain's path.
Environment variable:
TOOLCHAIN_PATH=/opt/brcm/hndtools-mipsel-uclibc
(This environment variable is not really necessary in the build process. It is used to indicate the target installation path that passes to configure script.)
zlib:
tar zxf zlib-1.2.2.tar.gz
cd zlib-1.2.2
./configure --prefix=$TOOLCHAIN_PATH
make CC=mipsel-uclibc-gcc 2>&1 | tee build.log
make install
libid3tag:
tar zxf libid3tag-0.15.1b.tar.gz
cd libid3tag-0.15.1b
RANLIB=mipsel-uclibc-ranlib AR=mipsel-uclibc-ar CC=mipsel-uclibc-gcc ./configure --prefix=$TOOLCHAIN_PATH --enable-static --disable-shared --host=mips-linux
make 2>&1 | tee build.log
make install
libmad:
tar zxf libmad-0.15.1b.tar.gz
cd libmad-0.15.1b
RANLIB=mipsel-uclibc-ranlib AR=mipsel-uclibc-ar CC=mipsel-uclibc-gcc CXX=mipsel-uclibc-g++ ./configure --prefix=$TOOLCHAIN_PATH --enable-static --host=mips-linux --disable-shared
make 2>&1 | tee build.log
make install
madplay compilation:
After installed all the libraries provided above, you could now compile madplay:
tar zxf madplay-0.15.2b.tar.gz
cd madplay-0.15.2b
LIBS="-lm -lz" RANLIB=mipsel-uclibc-ranlib AR=mipsel-uclibc-ar CC=mipsel-uclibc-gcc CXX=mipsel-uclibc-g++ ./configure --prefix=$TOOLCHIAN_PATH --enable-static --host=mips-linux
make 2>&1 | tee build.log
If no error was found during the compilation, a binary file (`madplay`) should be created within the path of madplay-0.15.2b/ . As additional libraries like libmad and id3tag are linked statically, you could just install this single binary to your access point.