similar to: Compiling libogg and libvorbis using MinGW

I am using libogg, libvorbis, and libvorbisfile in my most recent project. One of the build environments that my project must build on is MinGW. http://www.mingw.org/ Unfortunately, it seems that there are a few (possibly) minor problems with the libogg and libvorbis build processes which prevent me from building them under MinGW. One is that both of them reference header _G_config.h which

Hi folks,. I'm working on a project on Irix 6.3 using CC (not GCC) and the .o32 object format (not n32) and would like to incorperate ogg-vorbis. Is there any way to configure the libogg/libvorbis makefiles to work with CC? (Or does anyone know how to arm-twist GCC under Irix 6.3 into producing o32 object files?) Thanks super-much for any help, Mike <p>--- >8 ---- List

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

Hi, today I learned that libogg 1.3.0 had been released in August 2011. Curiously, there seems to have been no announcement mail here, and it is not being mentioned on <http://www.xiph.org/press/> either. Is that on purpose? Is there some other channel I could subscribe to in order to learn about updates? Freecode.com doesn't have up-to-date info either (though I just submitted a 1.3.0

Hello, I am developing a game engine which will support Ogg Vorbis playback. If I were to use LibOgg and LibVorbis, would I then have to release my own product under BSD, thus requiring anyone who created games with it to do the same and reference Xiph.org in their game's credits? While I can definitely include a license file with my library, enforcing my own end-users to do the same would be

All, Monty has made some improvements to the vorbis reference implementation, and we're ready to do a new release. Please sanity check the release candidate at http://people.xiph.org/~giles/2007/libvorbis-1.2.0rc2.tar.bz2 And let us know if there are any problems. The plan is to make an official release on Wednesday. Changes since the 1.1.2 release: * new ov_fopen() convenience

Hi there, I maintain the libvorbis, libogg and vorbis-tool package for Fink <http://finkproject.org/ >. Recently I had time to wonder about those again. In particular, since I was informed libsndfile self-tests fails with 1.2.0, but not with a version dubbed 1.2.1rc1 somebody sent me. Also trunk seems to contain security fixes. In https://trac.xiph.org/browser/trunk/vorbis/CHANGES

Hi I'm trying to compile my game project (that depends on libvorbis) for the win32 platform. I use mingw (both native in linux and inside cygwin) to achieve this. But I can't get libvorbis to work because of a dependency problem with libogg. libogg seems to have a file (os_types.h) that depends on an include-file called _G_config.h. This file is supposed to contain some system-specific

Hello I'm trying to install libogg and libvorbis, I successfully downloaded and compiled libogg but when I try to ./configure libvorbis I get an error saying: *** Could not run Ogg test program, checking why... *** The test program compiled, but did not run. This usually means *** that the run-time linker is not finding Ogg or finding the wrong *** version of Ogg. If it is not finding Ogg,

Hi all, Those of you uninterested in classic MacOS as a target will probably want to skip this email. I'm revisiting this platform, trying to get music going for the game I'm working on. We're obviously using OggVorbis on the other platforms we support (osx, linux, win32). The problem is that our classic MacOS build is currently under MPW/MrC. I can compile libogg/libvorbis fine

Hi all. I found some references to a problem similar to mine in the archives, but none of the solutions posed there worked, so I'm left to ask again. I'm running Debian 2.2r5, libc6, and as far as I know all other necessary libraries for compilation. libao and libogg compile and install fine, but when I try run ./configure for libvorbis, it fails and says it can't find libogg.

Using libvorbis (1.3.5) I wish to extract the raw vorbis packets.  I've built some simple code on the excellent libvorbis API overview on the xiph.org site, but the example relies on the ogg_packet struct for final output and input to decoder, and shows now examples on how to do without it. Taking a look at the vorbis_bitstream_flush() function, which in the overview is the last step before

L'octidi 18 pluviôse, an CCXXV, Miscellaneous a écrit : > I've built some simple code on the excellent libvorbis API overview on > the xiph.org site, but the example relies on the ogg_packet struct for > final output and input to decoder, and shows now examples on how to do > without it. Why do you not want it? It is just a simple C struct to carry the packet's metadata.

Hello, I'm running into problems while trying to build libvorbis. My build platform is Solaris 10 (sparc) (11/06) with GCC 3.4.6. The build fails with the following error : Making all in examples gmake[2]: Entering directory `/afs/cad.njit.edu/u/a/n/andym/ftp/freeware/multimedia/ogg/libvorbis-1.2.0/examples' gcc -DHAVE_CONFIG_H -I. -I.. -I../include

I'm pleased to announce the release of new versions of our Ogg and Vorbis reference implementation libraries. These are bug fix releases, with no new features. Particularly important is a fix for a pointer aliasing bug triggered by the new gcc 4.x optimizer. Because of this we strongly recommend that all gcc-based users upgrade, i.e. those on GNU/Linux and MacOS X, for example. The new

I'm pleased to announce the release of new versions of our Ogg and Vorbis reference implementation libraries. These are bug fix releases, with no new features. Particularly important is a fix for a pointer aliasing bug triggered by the new gcc 4.x optimizer. Because of this we strongly recommend that all gcc-based users upgrade, i.e. those on GNU/Linux and MacOS X, for example. The new

Xiph.Org is pleased to announce a full release of libogg 1.2.1 and libvorbis 1.3.2. This is not a coordinated release, it was merely convenient to do a release cycle for both at the same time. Changes and fixes in the new libogg release include: * Various build updates (see SVN) * Add ogg_stream_pageout_fill() to API to allow applications greater explicit flexibility in page sizing. *

Xiph.Org is pleased to announce a full release of libogg 1.2.1 and libvorbis 1.3.2. This is not a coordinated release, it was merely convenient to do a release cycle for both at the same time. Changes and fixes in the new libogg release include: * Various build updates (see SVN) * Add ogg_stream_pageout_fill() to API to allow applications greater explicit flexibility in page sizing. *

Xiph.Org is pleased to announce a full release of libogg 1.2.1 and libvorbis 1.3.2. This is not a coordinated release, it was merely convenient to do a release cycle for both at the same time. Changes and fixes in the new libogg release include: * Various build updates (see SVN) * Add ogg_stream_pageout_fill() to API to allow applications greater explicit flexibility in page sizing. *

since there's already a Python wrapper for libogg and libvorbis, it occurred to me: Why not write a Python wrapper for libogg and libvorbis? http://dingoskidneys.com/oggpy/ this is the 0.001 release. "release early.." it requires Boost.Python, possibly CVS Boost.Python, available from http://boost.org/ partly because it's not finished but mostly because it's written with