Apparently Ogg Vorbis doesn't support Windows

[torkell]

So, I thought it might be worth downloading the current 1.1.1 version of oggenc, as apparently it's a lot better. Silly me.


Problem #1: The vorbis people apparently don't believe in up-to-date binaries for win32. Solved by deciding to build from source. I'll just need to download, unzip, and run nmake, right?

Problem #2: While they provide MS Visual C++ projects, they neglect to convert the line endings to windows style. Solved by uploading to a random ftp site in binary, and then downloading in ascii mode.

Problem #3: No, MSVC will not automagically include all the project files in the current directory just by opening a workspace containing an empty project

Problem #4: Apparently I need to download (and presumably compile) libvorbis to make it work. I'll just pick up and compile libogg while I'm at it, shall I?

Problem #5: libvorbis depends on libogg. Specifically, libvorbis depends on the libogg files being in a directory called "ogg" in the include path, or in a directory called "ogg" in one of "..\..\ogg\include;..\include;..\win32\src;..\..\vorbis\lib" where the current directory is "D:\blah\libogg\win32". Solved by removing the "lib" prefix.

Problem #6: vorbis-tools\oggenc\encode.c(176) : error C2143: syntax error : missing ';' before 'type' followed by vorbis-tools\oggenc\encode.c(183) : error C2065: 'bitrate' : undeclared identifier


At this point I decide it's too hard and give up. And don't you dare suggest that I should debug someone else's code that should Just Work.

How on earth do all you Unix/Linux/BSD people cope with building everything from source?

Comments

[ralesk.livejournal.com]

They blame Windoze for being obnoxious, because “it works” for them.

BTW, I’m endlessly pissed off at the idiocy of the IceCast people for similar reasons (only that they didn’t provide windows binaries for a good while, at all, period).

Fucking hate the “windows sucks, use 'nix” attitude.

[pewterfish.livejournal.com]

Building from source tends to work a lot better on Linux boxen, mainly because the developers tend to be working in said system and understand it well. The result is something that simply flies along in situations where everything is set up as expected, and falls over messily otherwise, as you have seen.

In order to build windows binaries, the developers would first need a Windows-based PC, which cannot necessarily be assumed. In summary, I suggest that their Windows maintainer (whose responsibility it is to package the software for use on Windows machines, as you're probably aware) is on crack and should be shot.

Problem 6 is ... interesting. Could be an honest typo, but /might/ also be triggered by your solution to problem 5.

Conclusion: Not impressed by the Ogg Vorbis Windows maintainer. Building binaries shouldn't be that hard, but the problems you've encountered (particularly with MSVC projects) are unacceptable. Someone isn't doing their job and, since they're not being paid to do so, it's kinda hard to make them. If it helps any, this annoys me too.