[Vorbis-dev] Status of Windows builds for libvorbis/libogg

Andre Pang Andre.Pang at csiro.au
Wed Jan 5 07:29:37 PST 2005


Hi all,

I've just done a quick check of the libvorbis Visual C++ 6.0 project on 
Windows, and am happy to say that both libvorbis and libogg build fine. 
   (Theora isn't quite so lucky -- see the theora-dev mailing list for 
details on that.)  There are two suggestions I can make, though:

     1.  To build properly, the directories must be checked out with 
certain names, and in paths relative to each other.  Specifically, both 
libogg and libvorbis must be checked out in the same directory, and 
libogg must be checked out to directory named "ogg".  (libvorbis can be 
checked out to whatever directory name you like, although it's strongly 
recommended to call it "vorbis", since that'll make it work with 
properly with the theora Windows builds.)

         Because of the particular directory structure requirements, I'd 
suggest having a Subversion checkout path which uses svn:externals to 
pull down all the appropriate required libraries, so that a Windows 
developer can check out a single URL and have all the files sitting on 
their local machine in good order.  It looks like 
http://svn.xiph.org/trunk/win32sdk did this for CVS, but it needs to be 
upgraded to work with Subversion now.

     2.  Along with the Visual C++ 6.0 projects (the .dsp/.dsw files), 
it would be good Visual Studio .NET 2003 solution and project files 
(.vcproj/.sln), so that Windows developers who are using the more recent 
versions of Visual Studio can compile stuff too.  Zen (illiminable) has 
already done this in the oggdsf/ tree.  I think the best approach would 
be to coordinate with him and the respective codec maintainers on 
getting the VS.NET 2003 files into the original 
ogg/vorbis/theora/speex/(flac?) trees, not only so that we gain support 
for VS.NET 2003, but also so that the oggdsf tree can just use 
svn:externals to remain in sync with the trunk, rather than re-importing 
  the source trees of each of the codecs into the oggdsf tree.

Unless there are any objections, I'm happy to go ahead and make these 
changes over the coming week or two.


-- 
: André Pang (x4180)
: Software Engineer, Networked Media : CeNTIE


More information about the Vorbis-dev mailing list