Joined: July 2004
||Posted: Oct. 03 2007,13:34
Yes, there are multiple issues.
|Is there any issue with just grabbing the play binary and including that in one of my Exts|
First, the only actual executables are "sox" and "soxmix". The play and rec commands are simply a shell script and a link that run the sox command using specific parameters. The actual command is much larger than 6k.
Second, the application was linked to libmp3lame, which is also not a part of DSL. This strengthens the need for the play script, as that script sets up LD_LIBRARY_PATH to include the libmp3lame directory.
Third, the application cannot legally be distributed without also including the license file(s).
So ultimately, your only options in reducing the size of the package are removing only the soxmix executable and help files, or recompiling the application without mp3 support. The minimum files required to use play in this case, in a new extension, are the play script, the non-mp3 sox executable, and the license files.
You're looking at an old version of sox. The newer version is uci. In either case, though, as long as a binary was built with a compatible c library/compiler it can usually be made to work by including support files and/or setting up the runtime environment to accommodate the program.
|Also if the binary is so system specific then how can sox possibly work like that as its a precompiled tar.gz|
I can't answer that question. The problem could have several sources, and no one can know unless we know specifically what differences there are between your personal USB and CD installations. A first guess would be that you have the sox mydsl package saved to your usb device.
|Also why does play appear on a USB install and not on a CD boot.|