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 using the build system in the module "win32sdk"? All
the
CW> issues you bring up have been solved there. All versions of the
CW> libraries work -- static and dynamic, debug and release.
Yes, but this module seems to have been checked in after RC2, which is
what most people use for "production" stuff. If I do:
cvs co -r vorbis1_0_public_release_candidate_2 win32sdk
I get an empty directory... :)
It doesn't seem advisable to use the head branch except for
experimentation purposes, etc. Please correct me if I'm wrong.
--- >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@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.
