On Tue, 29 Aug 2006 17:50:12 +0100 sacha <[EMAIL PROTECTED]> wrote: > I've had a rummage on google/GMANE/the wiki and played with the configure > flags but haven't found the answer.
> I need to compile transcode on one machine in such a way that it will work > on another. At the moment it seems that paths get hardwired into the > executables at compile time, such that if the target machine doesn't share > the same directory structure, the binaries won't find their codec modules > etc. Yes, path are hardcoded into transcoded binaries. There are some plans to improve this for future, though. > The symptom is that I get error messages from the transcode command at > runtime that suggest it is trying to dynamically load modules: > > transcode] > warning : > /some/where/on/my/build/machine/transcode-1.0.2/lib/transcode/export_im.so: > cannot open shared object file [...] > Is there an answer? What about playing with --prefix configure option and prefix/DESTDIR makefile variable? Combininb both should solve your issues. Best regards, -- Francesco Romani - Ikitt ['people always complain, no matther what you do'] IM contact : (email first, Antispam default deny!) icq://27-83-87-867 known bugs : http://www.transcoding.org/cgi-bin/transcode?Bug_Showcase tiny homepage : http://fromani.exit1.org (see IDEAS if you want send code!)
