Hi, Aha, we see the problem. In our environment we always ran application from the same directory were codecs were located, so there was no problem. (Current directory is in codecs search path too). As a temporary solution you may do the same or compile some codecs you're interested in as a statically loaded instead of dynamically loaded.
We're going to release fix for this soon. On 5/30/08, Karsten Schubotz <[EMAIL PROTECTED]> wrote: > I've made a cross-compilation of sipXtapi for arm-linux, and installed the > libraries in > special folders. > I used the configure- option „–with-codec-bin-path= /home/devel/target/bin". > The installation of the PlaceCall example is in the same folder: host:/> > home/devel/target/bin > The target-folder is the root file system of my arm-linux target. > When I start the application from the arm-linux target by using the network > file system, > I have to go into the directory: target:/> bin > and start the PlaceCall example. > The codec's are installed there too: target:/> bin > But the application searched for them at: target:/> home/devel/target/bin > > They couldn't be found in that folder. It don'1 exists. > > So far I've made this directory manually and copied the codecs in it. The > application is working then. > Is it possible to refer to the codec search-path during installation? I > think the search-path have to be another than the installation-path? -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
