similar to: Updated Win32 SDK build environment

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. -

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

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

I made some changes to the win32 build environment. The build scripts now use msdev to build all the projects (kind of like Jack originally had it.) If building with nmake and makefiles is desired, such as if it is expected that the sdk will be copied to an environment which has a version of MSVC older then version 6 -- simply set the environment variable USENMAKE to any value and the

The Win32 SDK directory layout seems to need a small update in my eyes. Here's why: 1. Debug symbols get overwritten Problem: When the project files in the vorbis/win32 build, all temporary files of vorbis, vorbisfile and vorbisenc go into Dynamic_Debug (for the dynamic debug build as an example). The problems arise, when someone wants to debug the code. Since Visual C++ puts the symbols

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, Thanks for provoding the snapshot. Now it refers to following folders which are not included in the package! ../../pthreads ../../oggvorbis-win32sdk-1.0.1/include 1) Can I use http://svn.xiph.org/trunk/ogg insted of oggvorbis-win32sdk-1.0.1? 2) Where do I get pthreads? 3) Is svn for libshout available for public read access? Where? - Altu Faltu ----- Original Message ----- > >

> 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

Yes, it works now. Thank you very much. -----Original Message----- From: Chris Wolf [mailto:cwolf@starclass.com] Sent: 05 September 2001 10:12 To: vorbis-dev@xiph.org Subject: Re: [vorbis-dev] Problems trying to run the examples in windows vorbis sdk On 9/4/2001 at 6:00 PM Pablos-Sanchez, Rolando wrote: >I have just downloaded the vorbis sdk for windows, for researching >purposes. >

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

It was recently brought to my attention by "Ram'on Garc'ia Fern'andez <ramon@jl1.quim.ucm.es>" that there is yet an even simpler solution to the issue of cross-DLL access of variables in the data segment. Although a variable may be exported either from the module definition file, or explicitly via _cdeclspec(dllexport) -- unlike procedures (functions), it is mandatory

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"

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

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

If You want to compile vorbis libraries under win32 environment you can experience some problems: 1) If you unzip vorbis libraries, you will have 3 directories: "libogg-1.0", "libvorbis-1.0" and "vorbis-tools-1.0". You need to rename them to "ogg", "vorbis", "vorbis-tools". Otherwise batch files or even dsp project files, won't work.

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

I'm trying to implement vorbis into our game engine as a substitute to mp3 and wma encoding. And I have some questions/suggestions in how #includes are done in vorbis. Right now ogg and vorbis stuff relies on ogg and vorbis include paths being in global (or local) include path environment. This could easily be avoided by using relative includes in vorbis: #include

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

Hi I am using ogg-vorbis win32 SDK 1.0 [ VC++ 6.0 , Windows XP ] I am trying to use the function "vorbis_analysis_headerout() ; " When I called the function in a stand alone small C progam it worked , but when I tried to use the same function as part of some big project it failed saying "Access violation in Vorbis.dll " and the application closed. Any clue ??? Thank you,

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