I am trying to update the alsa-lib that is available in ti-sdk v07.
that sdk has alsa-lib v 1.0.26 and I want to upgrade the lib of that pkg to the latest open source alsa-lib (v1.1.1)
I have downloaded the tar ball for alsa-lib from the alsa web and run following commands to build and install the package into the ti-sdk targetnfs so that when I create the sdcard to boot my am335x board, I have the new alsa-lib installed in there and can run alsa cmds. Unfortunately, when I run alsa cmds on the target, they can't find the installed libs because of wrong path: the newly built alsa-libs have hardcoded my ti-sdk path into the lib.
here are my steps:
downloaded alsa-lib version 1.1.1 from http://www.alsa-project.org/main/index.php/Download
1. Untar the pkg into my workspace of my linux machine at /home/<username>/
Source the build environment to pick up the variables needed for the SDK:
-
$cd ~/ti-sdk-am335x-evm-07.00.00.00/linux-devkit/
$ source environment-setup
$ cd ../../alsa-lib-1.1.1/
2. cross compile and install alsa-lib-1.1.1:
-
> sudo ./configure --host=arm-linux-gnueabihf --prefix=~ti-sdk-am335x-evm-07.00.00.00/targetNFS/usr
-
> sudo make
> sudo make install
when I run any audio alsa app from the target console, I get something like :
can't find /home/<username>/ti-sdk-am335x-evm-07.00.00.00/targetNFS/usr/lib/<an alsa lib>.
So basically, the path is not rooted!!! the libs built above seem to have preserved the given hardcoded path in --prefix or ti-sdk environement variables so the path have not been rooted when the library are built!
Anyone know the trick to get such new pckg libs be cross compiled and properly install in the sdk targetNFS without hardcoded path name?
