[vorbis-dev] Problems with vorbis sdk

[John Denton]

Hi Hervé,

Perhaps I can make up for my hijack :-)

"Yes" doesn't seem a very informative response? That's because you are a
Windows user - you've been coddled :-)

CVS is a version control system  - an essential tool when several remote
people are programming on a particular system. And there seem a number of
remote people programming Ogg Vorbis (very remote people :-) This particular
system is from an outfit called Concurrent Version Systems and (as far as I
can see) you have to go through this to get at any source code. I don't have
the URL on hand at the moment but a search (I used Google) will find it. On
their web site you can download CVS and several pages of 'help'. I hope you
aren't paying UK phone rates :-)

You'll need to do some reading and make a start on the CVS learning curve
before you do anything else. Once you have installed the CVS, go on line
(IE) to your home site (or whatever) then kick up WinCvs. You will need to
enter some Linux type rubbish
(:pserver:anoncvs at xiph.org:/usr/local/catroot - make sure you don't miss the
colon after org) establishing the 'CVSRoot' and a password - anoncvs. Then
you need to know which 'module' you want to access - and select this from
one of the CVS menu items.

There is a page on the xiph.org site ('naming' I think) which explains some
of this and outlines the available modules.

I understand the necessity of such a system for uploads and version checking
between programmers. Why its necessary for downloading - for those of us who
just want to have a look at the latest available - I really don't know. I
think its to do with the Linux frame of mind..

J.
----- Original Message -----
From: Hervé Thouzard <hthouzard at rsi.fr>
To: <vorbis-dev at xiph.org>
Sent: Thursday, September 13, 2001 10:12 AM
Subject: Re: [vorbis-dev] Problems with vorbis sdk

> Hi Chris,
>
> >Check out the head revision of "ogg", "vorbis" and win32sdk go into
> >the win32sdk directory and run makesdk.bat.  If that doesn't work,
> >let me know.
> in the csv ?
>
> Bye,
> Hervé
>
> *********** REPLY SEPARATOR  ***********
>
> On 9/12/2001 at 1:41 PM Hervé Thouzard wrote:
>
> >Hi John,
> >
> >    As I am the original author of this subject, I would like
> >to ask my question again "how and what to do so that
> >this sdk can be use under Windows with Visual C or
> >any other C compiler ?"
> >
> >Thanks in advance,
> >
> >Bye,
> >Hervé
> >
> >----- Original Message -----
> >From: "John Denton" <dentons at onetel.net.uk>
> >To: <vorbis-dev at xiph.org>
> >Sent: Wednesday, September 12, 2001 10:44 AM
> >Subject: Re: [vorbis-dev] Problems with vorbis sdk
> >
> >
> >> Hi Chris,
> >>
> >> Many thanks..
> >>
> >> I hadn't considered actually rebuilding the dlls as such, but I'll take
a
> >> look at it - given the time. I was actually scanning through some of
the
> >> lines you mention late last night, after reading a couple of other
> >messages
> >> on the list..
> >>
> >> Average user I can manage, if I really put my mind to it.. :-)
> >>
> >>
> >> J.
> >> ----- Original Message -----
> >> From: "Chris Wolf" <cwolf at starclass.com>
> >> To: <vorbis-dev at xiph.org>
> >> Sent: Wednesday, September 12, 2001 12:31 AM
> >> Subject: Re: [vorbis-dev] Problems with vorbis sdk
> >>
> >>
> >> >stepping through the code it fails on the call to vorbis_encode_init.
I
> >> >can
> >> >place the two lines opening the i/o files (the only file access which
> >> >precedes that call) after this call and it still fails at the call to
> >> >vorbis_encode_init. This would seem to me to indicate that the failure
> >is
> >> >in
> >> >
> >>
> >> I checked in some fixes to solve this problem when building DLLs int
the
> >> MSVC environment.
> >> (and I moved those code modules at Monty's request out of vorbis/lib to
> >> vorbis/win32/src)
> >>
> >> The fixes are only brought in when _MSC_VER is defined, which is done
> >> implicitly when compiling
> >> with MSVC.  I could have choosen to turn on that code with WIN32, but
was
> >> concerned that the issue
> >> was confined to the MSVC environment, not necessarliy other windows
> >compiler
> >> environments, such
> >> as Cygwin GNU gcc, or Borland.
> >>
> >> If you want to see if the fixes work under Borland, and you are
building
> >> vorbis.dll, AND a separate
> >> vorbisenc.dll, then try:
> >>
> >> when building vorbis.dll, then define VORBIS_DLL and
> >> STANDALONE_VORBISENC_DLL
> >> when building vorbisenc.dll just define STANDALONE_VORBISENC_DLL
> >>
> >> Check the following files:
> >> vorbis/lib/registry.c                       r 1.10
> >> vorbis/lib/vorbisenc.c                    r 1.15
> >> vorbis/win32/src/dllmain.c
> >> vorbis/win32/src/shmmap.h
> >> vorbis/win32/src/shmmap_c.h
> >>
> >> And wherever you see "#ifdef _MSC_VER", replace that with "#if
> >> defined(_MSC_VER) || defined(BORLAND)
> >>
> >> where "BORLAND" is whatever predefined precompiler switch indicating
the
> >> Borland compiler.  If that
> >> solves the dynamic linking problem for Borland, can you send me the
> >patches?
> >>
> >> Also I would not waste time debating command line vs. windows, or
windows
> >> vs. UNIX, since the main
> >> goal here is to evangelize Ogg/Vorbis, not any specific OS -- we should
> >try
> >> to accomodate both.
> >> I personally prefer UNIX and command line tools, but wouldn't expect
the
> >> average end PC user to have the
> >> same sentiment.  However, I would like to see the average PC user
switch
> >> from mp3 to ogg, so I think it's
> >> important to support ogg on windows.
> >>
> >>
> >> --- >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.
> >
> >
> >--- >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.
>
>
> --- >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.