Better yet, post your (I assume) cleaned-up sources, so that we can build it ourselves.
Is it just me, or is distributing a set of patches just an absolutely horrid way to do things?
Any interest? If so, I will post the binary.
Yes and possible have rarewares distribute the binary or host it externally. I will place a link to it in the wiki page when I get the opportunity! Thanks.
I guess I would be able to produce a patch against the Lancer patches - but would this be at all useable to anyone?
diff -Naur aotuv-b5.7_20090301/ aotuv-b5.7_20090301-lancer/ > aotuv-b5.7_20090301-lancer.diff
Do you have rarewares' contact info ?
It is twice as fast as mainstream oggenc.
Unfortunately it accepts only wav files as input. Could you please add flac support?
I will try to encorporate Aoyoumi's latest version. It will be a good test for Git ;-)
FLAC support now added. I will try to encorporate Aoyoumi's latest version. It will be a good test for Git ;-)
You used aotuv-b5 version of 2006-10-24. Do you plan to make a binary of the latest aotuv-b5.7 (2009-03-01)?
~/src/lancer/vorbis-lancer-gcc$ file oggenc oggenc: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), not stripped~/src/lancer/vorbis-lancer-gcc$ ldd oggenc linux-gate.so.1 => (0xb7fae000) libogg.so.0 => /usr/lib/libogg.so.0 (0xb7f63000) libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7f3d000) libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7ddf000) /lib/ld-linux.so.2 (0xb7f94000)~/src/lancer/vorbis-lancer-gcc$
I compiled your snapshot vorbis-lancer-gcc-master.tar.gz locally by running ./build-script. The result here are not a static build and seems to have compiled my systems libogg in dynamically:
If you want to get a statically linked binary, do the following from the ogg-aoTuVb5-lancer directory (i.e. the root):1. $ ./build-script (if you haven't done this already)2. $ cd vorbis-tools-1.2.0/oggenc/3. $ make clean; make4. Copy the last gcc line on your console, paste it on your command line and add the -static switch. Execute it.5. $ cd ..6. $ make install7. The binary is now in ogg-aoTuVb5-lancer/out/bin
/usr/bin/ld: attempted static link of dynamic object `/usr/lib/libogg.so'collect2: ld returned 1 exit status
$ ./oggenc -q5 Luckie.wav -o Luckie.oggOpen with wav-module: WAV file readerEncoding "Luckie.wav" to "Luckie.ogg" at quality 5,00Mode initialisation failed: invalid parameters for quality
Does your build machine have libogg, liborbis and libflac installed? Mine doesn't.
autoconf/automake works in linux x86, linux ARM, UNIX x86, UNIX Sparc, .... list goes on. Not only that, but autoconf is old and tested.
Now, about your comment of not being able to update b5 to b5.7... Is that because you think you cannot do as good as lancer is, or because you don't know about intrinsics?
vi and ed are also old and tested, work in Linux, Sparc, HP-UX, Irix, etc. Why not use those? :-)
First thing is to profile OggEnc - applications use 5% of the code 95% of the time. We should find out where the 'expensive' functions are, and concentrate on those.
My build fails anyway, somethings wrong with it