[vorbis-dev] access violation in ov_open using VC6

[John Edwards]

I have compiled a complete set of static and dynamic, release and debug libs
using MinGW32 GCC 3.3.3. These are currently available at:
http://homepage.ntlworld.com/jfe1205/oggvorbislibs-SDK-win32GCC.zip

I should be grateful if these were subjected to some testing. Once confirmed
as OK, I'll post these to http://www.rarewares.org where they will be
generally available.

John

----- Original Message ----- 
From: "Ryan Ashley" <Lord_Dakron at hotmail.com>
To: <vorbis-dev at xiph.org>
Sent: Wednesday, March 10, 2004 4:50 AM
Subject: Re: [vorbis-dev] access violation in ov_open using VC6

<p>> I'm not complaining, I was pointing the problem out.  I think the best
> solution (for now) is to compile the libraries with Borland, then another
> set with Watcom, and a final set with MSVC.  That would be an excellent
> work-around until somebody finds the exact problem.  In fact I think I'll
> try compiling the SDK using Borland and make a zip of them.  When I get
them
> done properly, I'll upload them to my private server and send a link.
>
> ----- Original Message ----- 
> From: "Michael Smith" <msmith at xiph.org>
> To: <vorbis-dev at xiph.org>
> Sent: Tuesday, March 09, 2004 8:43 PM
> Subject: Re: [vorbis-dev] access violation in ov_open using VC6
>
>
> > On Wednesday 10 March 2004 12:32, Ryan Ashley wrote:
> > > That's the problem, Mike.  You see VC++ stuff is 100% proprietary, and
a
> > > good portion of us don't use VC++ for work.  You should make some
> generic
> > > libraries for Win32 instead.  Use something standard like gcc/g++ or
> > > Borland, or even Watcom.  Then the worst thing people have to worry
> about
> > > are the makefiles, which can be cake to change between compilers.
Going
> > > through tons of Vorbis source to recompile just so Vorbis works is a
> pain
> > > though.
> >
> > Our libraries _are_ generic win32 libraries. Obviously, there are some
> > problems causing linking errors with other systems - I'm not a windows
> > expert, so I don't know what causes these, or how to fix them. If you
> could
> > suggest a fix, we'd be happy to make it.
> >
> > Using gcc/borland/watcom won't help at all with this - it'll just mean
we
> have
> > libraries which work on a _different_ compiler - and if we only work
with
> one
> > compiler, it may as well be the most widely used one (VC++). Obviously,
> > there's some low-level error causing this incompatibility, because for C
> code
> > (which vorbis is), unlike C++, these libraries _should_ be compatible
with
> > other compilers. Help us fix it rather than just complaining.
> >
> > Mike
> >
> > --- >8 ----
> > List archives:  http://www.xiph.org/archives/
> > Ogg project homepage: http://www.xiph.org/ogg/
> > To unsubscribe from this list, send a message to
> 'vorbis-dev-request at xiph.org'
> > containing only the word 'unsubscribe' in the body.  No subject is
needed.
> > Unsubscribe messages sent to the list will be ignored/filtered.
> >
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> Ogg project homepage: http://www.xiph.org/ogg/
> To unsubscribe from this list, send a message to
'vorbis-dev-request at xiph.org'
> containing only the word 'unsubscribe' in the body.  No subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
>

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.