similar to: Re: Win32 project files for libshout

Hi, The VC++ project workspace for ezstream refers to libshout project, which is not supplied with ezstream or libshout source distribution. Project: "libshout"="..\..\libshout-2.0\win32\libshout.dsp" - Package Owner=<4> Where do I get those files? Please help! - Altu Faltu -- ___________________________________________________________ Sign-up for Ads Free at

I updated the win32sdk build environment. To summarize: 1.) Added a "mkmak.bat" script to create, install and run an automation macro to perform makefile export from the command line. 2.) Updated makesdk.bat to utilize "nmake" and generated makefiles for performing builds. 3.) Added "sdk\build" which contains a complete build environment for building all the

> I'm still in hell trying to build for Win32. I've tried rebuilding the > project files from scratch, however I'm running into a very odd problem. Are you using the build system in the module "win32sdk"? All the issues you bring up have been solved there. All versions of the libraries work -- static and dynamic, debug and release. Chris --- >8 ---- List

If you are after a 1.0.1 SDK built in the same format as 1.0, and if the current CVS is firm for the release, then you can download the SDK from: http://homepage.ntlworld.com/jfe1205/OggVorbis-win32sdk-1.0.1.zip This is built from the current CVS using MSVC++6 SP5. If this helps speed up the release, great, otherwise, no problem, it kept me amused for a few minutes!! John <p>--- >8

Hi vorbis-devs, I use the Ogg Vorbis libraries built from the win32sdk in winlame. Since the rc2 DLL's are not functioning, I compiled them by myself. The apparent reason is that some data arrays like _residue_P were not shared among DLLs. I looked at the code, and found that IMHO dirty hack in vorbis/win32/src/shmmap*.h that maps the data arrays. Why not placing the data arrays in

hi, i hope this is not too "newbie-ish" but i've never programmed with static libs before. i've downloaded the win32sdk and try to build a simple wav->ogg/vorbis encoder, but the linker complained about several redefinitions. environment is visual studio .net 2003 on winxp and a standard mfc-app set up by this project-wizzard that comes with vs.net2003 using the default

Hi, I've been working with oggvorbis-win32sdk-1.0.1 and have a semi-hypothetical question. Let's suppose that, for whatever reason, I've allocated a block of memory, and I've loaded into this memory a perfectly valid ogg vorbis file. Now I'd like to decode this vorbis data, but I'm stuck calling ov_open() because I don't have a FILE*, I have a block of memory. (This

I found a problem with ov_raw_seek function in oggvorbis win32sdk 1.0. When i called this function it returned OV_EINVAL immediatelly. I solved the issue by replacing the ov_raw_seek by ov_pcm_seek, which worked perfectly, but i would like to use the raw variant due to performace reason . Is anybody aware of this strange behaviour ? Martin Cesky <p><p>--- >8 ---- List

Hi, I've just got around to moving from version 1.0 to 1.0.1. Now when I run my program, at least on Windoze, (haven't tried Linux yet), I get an Access Exception on the ov_open. Nothing else has changed. All I did was replace the lib and dll files that are in the win32sdk zip and re-build all, so it's the same the project files for for both builds. Here the snippet of code that

Greetings, I've just downloaded the Ogg/Vorbis Win32 SDK 'OggVorbis-win32sdk-1.0.1.zip' and made a test app to open an ogg file. But as soon as I call ov_open() the program crashes because of an access violation to address 0x00000010... This happens on both Release and Debug builds. The test app is simple: #include "vorbis/codec.h" #include "vorbis/vorbisfile.h"

Ok, so I've taken hold of this, and since this appears to be the only thing holding up 1.0.1, I have done what I think closes the loop...Based on the conversations here on the list I have made the following changes to the vc6 project files : - consistent runtime linking. They are ALL now using the Multithreaded static runtime. Hopefully this makes the generated DLLs the most portable. -

Hi I'm new with ogg and also with using third party libraries. I'm making a C++ PocketPC program and I need a simple wav->ogg encoder function. But as I have tried to use ogg vorbis libraries I don't know what or how to use them. I think that best way would be to use libogg 1.1.3 and libvorbis 1.1.2. Do I even need both of them, since I only need to have capability of

No you are not wrong, the win32sdk was never tagged. Monty, Jack, et. al.: Can I tag the head revision of just "win32sdk" with the rc2 tag? -- or some such tag as to point win32 people to overlay the rc2 freeze? I know this violates the normal source code control protocol of not touching freezes, but it may help with win32 builders of rc2. Just an idea... -Chris CW> Are you

The CVS tree seems so broken apart, the <> includes don't work out of the box. ie <ogg/ogg.h>. They are broken, how do I resolve this? I know the structure is there for a reason, but I don't know how to work with it and make the code compile... To top it all off... I am at a loss as to which sub dirs contain the source for the libs that I need to put together before I

I'm working on a win32 C++/MFC program, and I'm having trouble getting rid of a memory leak when writing vorbis comments. I've cut away everything except reading the file and then writing it out, and I still have a 256 byte mem leak (appended below). The code was modeled after vorbiscomment. It uses all the oggvorbis-win32sdk-1.0 static libs. I tried checking the mailing list

Hey all...for whatever reason when opening up the vorbis_vc6 project in Dev Studio bitwise.c and framing.c are still in the project. From my understanding these files are only in the ogg library now. If I try to compile the project as is, it fails because it can't find the files. Simple solution: Delete the two files. I just thought I'd give somebody a heads up.... Keep up the great

Hi Ralph, Two diffs. One for vorbis.def and the other for vorbisfile.def. Hope they work!! regards John -------------- next part -------------- A non-text attachment was scrubbed... Name: vorbisdef.diff Type: application/octet-stream Size: 256 bytes Desc: vorbisdef.diff Url : http://lists.xiph.org/pipermail/vorbis-dev/attachments/20031001/3b7df5ad/vorbisdef-0001.obj -------------- next part

We compiled the vorbis_example from WIN32SDK with Borland 5.0 under WIN98. When running, it ends in an address violation caused by ov_open (or ov_test as well). This happens no matter which Library we're using, or if we're trying to read from stdin or a FILE*(which was binary). thanks, michael <p><p>_________________________________________________________________ MSN -

At 10:21 PM 1/8/2005, you wrote: >Well, I see ezstream 0.2.0 is downloadable, so I downloaded it and tried >to compile. Unfortunately it won't compile for me. The configure >script runs fine. Here's the output of make. > >Joel > >ezstream.c:406: warning: unused variable `ret' >ezstream.c: In function `main': >ezstream.c:576: error:

found a bug..when i click on update metadata from the admin panel, i just get an eroor: Could not parse XSLT file Darrell On Tue, 14 Dec 2004 14:21:01 -0600, oddsock <oddsock@oddsock.org> wrote: > Just wanted to let everyone know that we are prepping for a 2.2.0 > release of icecast. Just as before, we are doing Release candidates > first, and if no bugs are reported, these will